← previous blocknext block →recent activity
Analyzing
Block #91,008,802
10 transactions · 9 stateful · 2026-07-28 08:22:00 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,008,802 · 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
1w03w04w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6d955786…1327
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0x107b89e4…470d
0x34b655…2a6f
4 touches
1 conflict
0x159aac52…c583
0x34b655…2a6f
2 touches
0 conflicts
0x27ebd644…fbdd
0x34b655…2a6f
2 touches
0 conflicts
0x2e6c7be1…d3e9
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity