← previous blocknext block →recent activity
Analyzing
Block #86,656,743
21 transactions · 18 stateful · 2026-07-09 16:14:05 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
0.52
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,656,743 · 21 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
3w04w15w06w17w210w311w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bc13458…e6d8
0x34b655…2a6f
6 touches
3 conflicts
0x342f88f5…2a06
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x8eed7e30…c1ef
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xcf504b9b…8df2
0x34b655…2a6f
6 touches
3 conflicts
0x0cb718be…e163
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 0x2bc134588d…dce6d8
Audit this contract →
← previous block·next block →recent activity