← previous blocknext block →recent activity
Analyzing
Block #86,673,272
23 transactions · 20 stateful · 2026-07-09 18:04:24 UTC
Parallelism
70/100
Blocked
55%
Avg conflicts / tx
1.43
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,673,272 · 23 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
2w03w14w25w36w47w59w621w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0x485ae99d…f26f
0x34b655…2a6f
14 touches
21 conflicts
0x0b2bec5d…6e4a
0x34b655…2a6f
12 touches
15 conflicts
0x157dbfb2…4089
0x34b655…2a6f
12 touches
15 conflicts
0x7523ad90…2ba5
0x34b655…2a6f
12 touches
15 conflicts
0xb3b959eb…7827
0x34b655…2a6f
12 touches
15 conflicts
0xb46ee126…a1a5
0x34b655…2a6f
12 touches
15 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
12 touches
15 conflicts
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
21 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity