← previous blocknext block →recent activity
Analyzing
Block #86,623,846
24 transactions · 18 stateful · 2026-07-09 12:33:00 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,623,846 · 24 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
1w02w14w18w09w111w012w113w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1ab
0xb1dbf0…c0d3
6 touches
3 conflicts
0x8a35acfb…d1ac
0xb1dbf0…c0d3
6 touches
3 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0xa7013be2…c0a8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x4a4c3d20…bd65
0x3bd359…433a
4 touches
1 conflict
0x6f845aff…9fc9
0x3bd359…433a
4 touches
1 conflict
0x062b2598…4e28
0x43cf54…7777
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: 0xb1dbf05f…b1c0d3
3 conflicts on slot 0x8a35acfbc1…6bd1ab
Audit this contract →
← previous block·next block →recent activity