← previous blocknext block →recent activity
Analyzing
Block #91,999,746
9 transactions · 9 stateful · 2026-07-31 19:29:39 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,999,746 · 9 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96b35b79…54f4
0x34b655…2a6f
4 touches
1 conflict
0xb56231db…9800
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6f58168d…ea24
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
0x34b655…2a6f
4 touches
1 conflict
0x791c302e…2f7b
0x34b655…2a6f
4 touches
1 conflict
0x431fa96d…6ac0
0x754704…b603
2 touches
0 conflicts
0x6bef2c97…ba12
0x754704…b603
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 0x96b35b79c6…0754f4
Audit this contract →
← previous block·next block →recent activity