← previous blocknext block →recent activity
Analyzing
Block #86,240,721
33 transactions · 23 stateful · 2026-07-07 17:51:34 UTC
Parallelism
91/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,240,721 · 33 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
4w014w017w018w120w021w124w226w127w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x278676c0…d15c
0x34b655…2a6f
6 touches
3 conflicts
0x45ea7a97…bbb3
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbd9491f7…dd92
0x34b655…2a6f
6 touches
3 conflicts
0x4e58f1d6…2fca
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x89999c15…fdac
0x34b655…2a6f
4 touches
1 conflict
0x9cfde8ba…c3af
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 0x278676c021…32d15c
Audit this contract →
← previous block·next block →recent activity