← previous blocknext block →recent activity
Analyzing
Block #102,060,255
20 transactions · 18 stateful · 2026-09-05 01:57:10 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,060,255 · 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
1w02w03w15w19w217w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5dd033b6…34b5
0x34b655…2a6f
6 touches
3 conflicts
0x024b482b…16b0
0x34b655…2a6f
4 touches
1 conflict
0x0ec07cf7…c0c9
0x34b655…2a6f
4 touches
1 conflict
0x1a2e73cf…5ff5
0x34b655…2a6f
4 touches
1 conflict
0x33b7fbba…64de
0x34b655…2a6f
4 touches
1 conflict
0x477cb4f5…11b4
0x34b655…2a6f
4 touches
1 conflict
0x56e0d685…c960
0x34b655…2a6f
4 touches
1 conflict
0x5faba84e…c77f
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 0x5dd033b6c4…ea34b5
Audit this contract →
← previous block·next block →recent activity