← previous blocknext block →recent activity
Analyzing
Block #91,098,510
7 transactions · 6 stateful · 2026-07-28 15:53:32 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,098,510 · 7 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
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfb4f8cd9…d014
0x34b655…2a6f
4 touches
1 conflict
0x0cc5cf9a…310d
0x34b655…2a6f
2 touches
0 conflicts
0x118c1867…8519
0x34b655…2a6f
2 touches
0 conflicts
0x169508f4…6844
0x34b655…2a6f
2 touches
0 conflicts
0x26e22910…e825
0x34b655…2a6f
2 touches
0 conflicts
0x26e22910…e826
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity