← previous blocknext block →recent activity
Analyzing
Block #84,426,994
11 transactions · 11 stateful · 2026-06-29 08:18:46 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,426,994 · 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
1w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd97b5939…4e9b
0x065c9d…c394
4 touches
1 conflict
0x56785e37…a197
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xba0e8edf…de6d
0x065c9d…c394
3 touches
1 conflict
0x1c04c6b7…f2b5
0x065c9d…c394
3 touches
1 conflict
0x612e6e25…4538
0x065c9d…c394
2 touches
0 conflicts
0xa6d9ad9d…91b5
0x065c9d…c394
2 touches
0 conflicts
0xe75cebb6…6b36
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-MON/USDC
1 conflict on slot 0xd97b59395c…e44e9b
Audit this contract →
← previous block·next block →recent activity