← previous blocknext block →recent activity
Analyzing
Block #91,131,329
10 transactions · 9 stateful · 2026-07-28 18:38:38 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,131,329 · 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2130a548…c1de
0x34b655…2a6f
4 touches
1 conflict
0xbc66586e…20fe
0x34b655…2a6f
4 touches
1 conflict
0xb75406fd…9760
0x34b655…2a6f
4 touches
1 conflict
0x1526b11f…8b21
0x34b655…2a6f
2 touches
0 conflicts
0x16c35bb4…2cdc
0x34b655…2a6f
2 touches
0 conflicts
0x468d132a…d7b8
0x34b655…2a6f
2 touches
0 conflicts
0x5d041208…74ae
0x34b655…2a6f
2 touches
0 conflicts
0x699d479b…4838
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 0x2130a548b9…31c1de
Audit this contract →
← previous block·next block →recent activity