← previous blocknext block →recent activity
Analyzing
Block #91,768,611
15 transactions · 15 stateful · 2026-07-31 00:06:52 UTC
Parallelism
87/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,768,611 · 15 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
1w02w04w05w16w17w08w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb566cc65…214d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5fe7e126…6dd2
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x74137b07…5880
0x34b655…2a6f
4 touches
1 conflict
0x99c5409a…25b7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe833d959…8666
0x34b655…2a6f
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 0xb566cc65b9…bf214d
Audit this contract →
← previous block·next block →recent activity