← previous blocknext block →recent activity
Analyzing
Block #86,737,933
24 transactions · 21 stateful · 2026-07-10 01:16:08 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,737,933 · 24 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
1w06w07w19w110w211w216w017w120w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92132ed7…2722
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x12573732…e891
0x34b655…2a6f
4 touches
1 conflict
0x7a9a468f…e378
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8e9a7d26…688c
0x34b655…2a6f
4 touches
1 conflict
0x9138a113…0d5f
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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 0x92132ed70f…762722
Audit this contract →
← previous block·next block →recent activity