← previous blocknext block →recent activity
Analyzing
Block #91,243,394
20 transactions · 16 stateful · 2026-07-29 04:02:21 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,243,394 · 20 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
4w05w16w07w08w111w013w215w117w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x989252a1…d812
0xa6afd3…d132
4 touches
1 conflict
0xe5bb3628…e5e8
0x34b655…2a6f
4 touches
1 conflict
0xf0d45ffd…89cf
0x34b655…2a6f
4 touches
1 conflict
0xfd8783dc…3725
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x529e53cf…38e4
0xa6afd3…d132
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: Kuru Exchange: Market-WETH/USDC
1 conflict on slot 0x989252a1e8…7ed812
Audit this contract →
← previous block·next block →recent activity