← previous blocknext block →recent activity
Analyzing
Block #86,713,749
12 transactions · 10 stateful · 2026-07-09 22:34:31 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,713,749 · 12 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
1w02w13w06w17w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x83058c4e…c7cc
0x34b655…2a6f
4 touches
1 conflict
0xbbee202a…8912
0x34b655…2a6f
4 touches
1 conflict
0xbbee202a…8913
0x34b655…2a6f
4 touches
1 conflict
0xdfd1344f…43f5
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x1a439162…b838
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6630d365…74ad
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
1 conflict on slot 0x83058c4edf…44c7cc
Audit this contract →
← previous block·next block →recent activity