← previous blocknext block →recent activity
Analyzing
Block #91,104,162
33 transactions · 22 stateful · 2026-07-28 16:21:58 UTC
Parallelism
91/100
Blocked
27%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,104,162 · 33 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
5w06w19w010w011w112w013w123w225w129w030w1
- 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
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0xad565e60…945a
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb80
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: Kuru Exchange: Market-WETH/USDC
1 conflict on slot 0xb566cc65b9…bf214d
Audit this contract →
← previous block·next block →recent activity