← previous blocknext block →recent activity
Analyzing
Block #86,986,034
22 transactions · 20 stateful · 2026-07-11 04:54:18 UTC
Parallelism
86/100
Blocked
30%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,986,034 · 22 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
1w02w05w06w18w110w114w015w218w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b856d86…7988
0x34b655…2a6f
6 touches
3 conflicts
0xf58b2d27…e4eb
0x34b655…2a6f
6 touches
3 conflicts
0x7b6d2deb…dde0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x576e9cfe…56d1
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 0x2b856d868a…697988
Audit this contract →
← previous block·next block →recent activity