← previous blocknext block →recent activity
Analyzing
Block #86,988,476
14 transactions · 14 stateful · 2026-07-11 05:10:37 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,988,476 · 14 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
1w03w04w17w09w110w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x008accc4…1da7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x619c81de…01b4
0x34b655…2a6f
4 touches
1 conflict
0x793d86d7…acc4
0x34b655…2a6f
4 touches
1 conflict
0x7ae44958…8593
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb678410a…0edb
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 0x008accc476…b51da7
Audit this contract →
← previous block·next block →recent activity