← previous blocknext block →recent activity
Analyzing
Block #86,926,630
12 transactions · 8 stateful · 2026-07-10 22:17:25 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,926,630 · 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
2w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9199a85a…acd9
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xd1db601b…c70d
0x34b655…2a6f
6 touches
3 conflicts
0xa412324b…90aa
0x34b655…2a6f
6 touches
3 conflicts
0x3d22c439…de6d
0x34b655…2a6f
6 touches
3 conflicts
0x0d05c2b3…bd7e
0x34b655…2a6f
4 touches
1 conflict
0x423dcdaf…12ec
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
6 conflicts on slot 0x9199a85ae5…d3acd9
Audit this contract →
← previous block·next block →recent activity