← previous blocknext block →recent activity
Analyzing
Block #84,357,236
17 transactions · 13 stateful · 2026-06-29 00:33:53 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,357,236 · 17 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
1w03w04w17w08w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7263b4fb…09dc
0xa6afd3…d132
4 touches
1 conflict
0xe02484a6…c32e
0xc8689a…ee79
4 touches
1 conflict
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001a
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002a
0x1b6862…e19c
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: Kuru Exchange: Market-WETH/USDC
1 conflict on slot 0x7263b4fb47…e309dc
Audit this contract →
← previous block·next block →recent activity