← previous blocknext block →recent activity
Analyzing
Block #86,964,522
18 transactions · 17 stateful · 2026-07-11 02:30:36 UTC
Parallelism
78/100
Blocked
24%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,964,522 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w09w211w313w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02f0ef4a…7144
0x34b655…2a6f
4 touches
1 conflict
0x05975727…7fcf
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0a0ac643…b698
0x34b655…2a6f
4 touches
1 conflict
0x1adc709e…d1ca
0x34b655…2a6f
4 touches
1 conflict
0x253a4108…aaaf
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6e90b9b1…dca8
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 0x02f0ef4ab4…c27144
Audit this contract →
← previous block·next block →recent activity