← previous blocknext block →recent activity
Analyzing
Block #91,284,073
10 transactions · 9 stateful · 2026-07-29 07:27:53 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,284,073 · 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
3w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd0e8089…4e3c
0x34b655…2a6f
4 touches
1 conflict
0x361f4a1b…1f14
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x4932cb23…a2a3
0x34b655…2a6f
2 touches
0 conflicts
0x4943c7e5…d013
0x34b655…2a6f
2 touches
0 conflicts
0x59cd6c8f…4e99
0x34b655…2a6f
2 touches
0 conflicts
0x5e4b65e1…ebe1
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 0xcd0e8089bb…aa4e3c
Audit this contract →
← previous block·next block →recent activity