← previous blocknext block →recent activity
Analyzing
Block #102,876,862
22 transactions · 21 stateful · 2026-09-07 22:49:53 UTC
Parallelism
77/100
Blocked
29%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,876,862 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w015w116w217w319w320w221w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad9f7641…a4ff
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00e5ba9d…5f4e
0x34b655…2a6f
4 touches
1 conflict
0x1609f128…4dc7
0x34b655…2a6f
4 touches
1 conflict
0x41469894…598f
0x34b655…2a6f
4 touches
1 conflict
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
1 conflict on slot 0xad9f7641df…d7a4ff
Audit this contract →
← previous block·next block →recent activity