← previous blocknext block →recent activity
Analyzing
Block #86,684,591
20 transactions · 18 stateful · 2026-07-09 19:19:59 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
1.1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,684,591 · 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
2w03w14w05w010w111w114w215w316w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x78860c4f…cade
0x34b655…2a6f
6 touches
3 conflicts
0xbbee4d2c…9b35
0x34b655…2a6f
6 touches
3 conflicts
0x818b0b44…ff6f
0x34b655…2a6f
4 touches
1 conflict
0x83dee4ed…fbad
0x34b655…2a6f
4 touches
1 conflict
0x94ed0437…073c
0x34b655…2a6f
4 touches
1 conflict
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0xa08f40b2…9a93
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity