← previous blocknext block →recent activity
Analyzing
Block #86,314,507
22 transactions · 17 stateful · 2026-07-08 02:04:17 UTC
Parallelism
77/100
Blocked
35%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,314,507 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w010w012w113w114w118w219w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xada5ad75…1d24
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7e047605…a58b
0xa6afd3…d132
4 touches
1 conflict
0x0dd3d3cd…7281
0x34b655…2a6f
4 touches
1 conflict
0x16a8cd0c…27bd
0x34b655…2a6f
4 touches
1 conflict
0x99701186…1cbf
0x34b655…2a6f
4 touches
1 conflict
0xdc921364…4680
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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 0xada5ad75a3…de1d24
Audit this contract →
← previous block·next block →recent activity