← previous blocknext block →recent activity
Analyzing
Block #86,657,767
19 transactions · 15 stateful · 2026-07-09 16:20:57 UTC
Parallelism
63/100
Blocked
40%
Avg conflicts / tx
0.47
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,657,767 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w18w215w316w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc0eb79d1…29a4
0x34b655…2a6f
6 touches
3 conflicts
0x4e068769…91ad
0x34b655…2a6f
6 touches
3 conflicts
0x84849074…1ca2
0x34b655…2a6f
6 touches
3 conflicts
0x219dd66f…0ce5
0x34b655…2a6f
4 touches
1 conflict
0x2bf5914f…c75d
0x34b655…2a6f
4 touches
1 conflict
0x398c3a27…6f7e
0x34b655…2a6f
4 touches
1 conflict
0x4560e5a8…b741
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity