← previous blocknext block →recent activity
Analyzing
Block #86,928,332
16 transactions · 13 stateful · 2026-07-10 22:28:46 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,928,332 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w19w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00e76a35…df2b
0x34b655…2a6f
4 touches
1 conflict
0x0129c52e…e6d1
0x34b655…2a6f
4 touches
1 conflict
0x04105a34…6eea
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x250c8181…eef2
0x34b655…2a6f
4 touches
1 conflict
0x29b4e629…a150
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 0x00e76a35c3…52df2b
Audit this contract →
← previous block·next block →recent activity