← previous blocknext block →recent activity
Analyzing
Block #86,504,241
22 transactions · 19 stateful · 2026-07-08 23:12:02 UTC
Parallelism
64/100
Blocked
47%
Avg conflicts / tx
1.32
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,504,241 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w28w39w410w513w119w521w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd99b3b64…1c95
0x34b655…2a6f
14 touches
21 conflicts
0x63c900f4…2600
0x34b655…2a6f
12 touches
15 conflicts
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
12 touches
15 conflicts
0x922c7ebd…6600
0xc8689a…ee79
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x9f653aa4…a15c
0x34b655…2a6f
6 touches
3 conflicts
0x485ae99d…f26f
0x34b655…2a6f
4 touches
4 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 0xd99b3b6441…7a1c95
Audit this contract →
← previous block·next block →recent activity