← previous blocknext block →recent activity
Analyzing
Block #86,883,623
26 transactions · 23 stateful · 2026-07-10 17:29:58 UTC
Parallelism
73/100
Blocked
26%
Avg conflicts / tx
0.42
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,883,623 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w08w19w211w318w422w525w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05e76e1b…39ec
0x34b655…2a6f
6 touches
3 conflicts
0x14fe1598…d0ba
0x34b655…2a6f
6 touches
3 conflicts
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x6016de75…62e0
0x34b655…2a6f
4 touches
1 conflict
0x6016de75…62e1
0x34b655…2a6f
4 touches
1 conflict
0x6b75f0c2…d323
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
3 conflicts on slot 0x05e76e1b2d…1839ec
Audit this contract →
← previous block·next block →recent activity