← previous blocknext block →recent activity
Analyzing
Block #86,617,610
30 transactions · 23 stateful · 2026-07-09 11:51:21 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,617,610 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w012w013w114w115w017w119w120w225w226w327w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
8 touches
6 conflicts
0x347327ff…3863
0x34b655…2a6f
4 touches
1 conflict
0x4caf91f9…8ab5
0x34b655…2a6f
4 touches
1 conflict
0x6f95cc9f…e9b5
0x34b655…2a6f
4 touches
1 conflict
0x7f2db611…3990
0x34b655…2a6f
4 touches
1 conflict
0xb6629430…e116
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
6 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity