← previous blocknext block →recent activity
Analyzing
Block #91,012,282
10 transactions · 9 stateful · 2026-07-28 08:39:36 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,012,282 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5559c2e5…928e
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc1aa38d0…a9f3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0fc81850…e472
0x34b655…2a6f
2 touches
0 conflicts
0x1b425cff…53d9
0x34b655…2a6f
2 touches
0 conflicts
0x1c8753e8…d214
0x34b655…2a6f
2 touches
0 conflicts
0x2015205e…6b1d
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 0x5559c2e594…d7928e
Audit this contract →
← previous block·next block →recent activity