← previous blocknext block →recent activity
Analyzing
Block #86,929,286
18 transactions · 16 stateful · 2026-07-10 22:35:07 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,929,286 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w29w010w011w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13e48618…af82
0x34b655…2a6f
8 touches
6 conflicts
0xba559de1…6d2c
0x34b655…2a6f
6 touches
3 conflicts
0x04105a34…6eea
0x34b655…2a6f
6 touches
3 conflicts
0xe727ab72…768b
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x44934f0e…b291
0x34b655…2a6f
6 touches
3 conflicts
0x5d7f309d…5145
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x13e48618f9…f3af82
Audit this contract →
← previous block·next block →recent activity