← previous blocknext block →recent activity
Analyzing
Block #86,959,541
39 transactions · 25 stateful · 2026-07-11 01:57:16 UTC
Parallelism
87/100
Blocked
48%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,959,541 · 39 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
1w013w118w219w120w221w022w123w226w327w029w130w231w333w234w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9355efee…7bcd
0x34b655…2a6f
10 touches
10 conflicts
0xbafb5860…9ddf
0xd32edf…ff58
7 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x64852187…6caf
0x34b655…2a6f
6 touches
3 conflicts
0x64852187…6cb0
0x34b655…2a6f
6 touches
3 conflicts
0x7ae44958…8593
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0x9355efee55…867bcd
Audit this contract →
← previous block·next block →recent activity