← previous blocknext block →recent activity
Analyzing
Block #84,358,367
26 transactions · 23 stateful · 2026-06-29 00:41:26 UTC
Parallelism
92/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,358,367 · 26 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
1w03w011w112w016w018w119w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7263b4fb…09dc
0xa6afd3…d132
4 touches
1 conflict
0xead14cec…4c53
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0x0b408000…9df1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…003d
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 0x7263b4fb47…e309dc
Audit this contract →
← previous block·next block →recent activity