← previous blocknext block →recent activity
Analyzing
Block #86,624,147
20 transactions · 16 stateful · 2026-07-09 12:35:00 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,624,147 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w212w018w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8eb0ac6b…a73a
0x34b655…2a6f
6 touches
3 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
4 touches
1 conflict
0x9fa5be00…fb16
0x34b655…2a6f
4 touches
1 conflict
0xa08f40b2…9a93
0x34b655…2a6f
4 touches
1 conflict
0xa3c36de0…3cf3
0x34b655…2a6f
4 touches
1 conflict
0xbc96083d…124d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdb3937e8…23cb
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 0x8eb0ac6bf2…4da73a
Audit this contract →
← previous block·next block →recent activity