← previous blocknext block →recent activity
Analyzing
Block #91,070,255
16 transactions · 14 stateful · 2026-07-28 13:31:18 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,070,255 · 16 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
2w03w04w15w28w39w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0a18f56…88a8
0x7b9256…1fb2
6 touches
3 conflicts
0x711ceb8d…5202
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xe1f61186…e2f8
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x11c8b1e0…ec39
0x7b9256…1fb2
6 touches
3 conflicts
0x11c8b1e0…ec3a
0x7b9256…1fb2
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: 0x7b9256fd…e21fb2
3 conflicts on slot 0xf0a18f569d…d288a8
Audit this contract →
← previous block·next block →recent activity