← previous blocknext block →recent activity
Analyzing
Block #86,059,330
15 transactions · 14 stateful · 2026-07-06 21:40:46 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,059,330 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w27w08w29w113w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c9eb6ea…7c39
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x6dfc6685…1adc
0x34b655…2a6f
6 touches
3 conflicts
0xc03846bb…73b3
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0x1aaf4996…65ec
0x34b655…2a6f
6 touches
3 conflicts
0x817e7ef6…61cb
0x34b655…2a6f
6 touches
3 conflicts
0x28681974…b88f
0xa6afd3…d132
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
6 conflicts on slot 0x0c9eb6ea19…6e7c39
Audit this contract →
← previous block·next block →recent activity