← previous blocknext block →recent activity
Analyzing
Block #84,266,284
11 transactions · 11 stateful · 2026-06-28 14:27:48 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,266,284 · 11 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d5c395b…6b5a
0xa6afd3…d132
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x7afd96cb…0dd6
0x065c9d…c394
2 touches
0 conflicts
0x7bda3c2e…9f47
0x065c9d…c394
2 touches
0 conflicts
0xa7719ca5…6781
0x065c9d…c394
2 touches
0 conflicts
0xb1d2a8a9…f61c
0x065c9d…c394
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 0x2d5c395b26…9d6b5a
Audit this contract →
← previous block·next block →recent activity