← previous blocknext block →recent activity
Analyzing
Block #91,411,595
13 transactions · 11 stateful · 2026-07-29 18:09:58 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,411,595 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59e89db7…661b
0x34b655…2a6f
4 touches
1 conflict
0x6c3907cd…5ac0
0x34b655…2a6f
4 touches
1 conflict
0xb9834665…e363
0x34b655…2a6f
4 touches
1 conflict
0xbed5ddf9…d1d2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x68bec689…fccd
0x34b655…2a6f
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
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 0x59e89db76f…e7661b
Audit this contract →
← previous block·next block →recent activity