← previous blocknext block →recent activity
Analyzing
Block #105,433,381
47 transactions · 41 stateful · 2026-09-16 22:02:47 UTC
Parallelism
79/100
Blocked
66%
Avg conflicts / tx
1.64
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,433,381 · 47 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w39w316w636w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xf7aa6468…55eb
0xd32edf…ff58
13 touches
21 conflicts
0x100812e9…12b7
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x645986fa…640e
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xb0f5d668…99ac
0x34b655…2a6f
6 touches
3 conflicts
0xb5dac821…b68b
0x34b655…2a6f
6 touches
3 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity