← previous blocknext block →recent activity
Analyzing
Block #102,468,362
20 transactions · 18 stateful · 2026-09-06 12:25:18 UTC
Parallelism
85/100
Blocked
50%
Avg conflicts / tx
0.7
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,468,362 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w18w111w012w013w114w215w216w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x98e2f231…ab6e
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x61a11641…fef0
0x34b655…2a6f
4 touches
1 conflict
0x6dc1811e…2588
0x34b655…2a6f
4 touches
1 conflict
0x87b41dd5…b410
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x8d616e7c…a6a1
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity