← previous blocknext block →recent activity
Analyzing
Block #86,984,319
20 transactions · 18 stateful · 2026-07-11 04:42:50 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
1.55
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,984,319 · 20 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
5w06w17w28w39w410w515w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb251976b…4938
0x34b655…2a6f
16 touches
28 conflicts
0x06aed19e…ca57
0x34b655…2a6f
12 touches
15 conflicts
0x922c7ebd…6600
0xc8689a…ee79
12 touches
15 conflicts
0x63c900f4…2600
0x34b655…2a6f
12 touches
15 conflicts
0x9f40a209…1193
0x34b655…2a6f
12 touches
15 conflicts
0xa1571d54…ae41
0x34b655…2a6f
12 touches
15 conflicts
0xbfdd8306…fa07
0x34b655…2a6f
12 touches
15 conflicts
0xe3ce9025…da31
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
28 conflicts on slot 0xb251976b09…9a4938
Audit this contract →
← previous block·next block →recent activity