← previous blocknext block →recent activity
Analyzing
Block #84,457,151
32 transactions · 24 stateful · 2026-06-29 11:39:46 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,457,151 · 32 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w18w29w010w111w215w016w118w220w321w222w426w527w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xe75cebb6…6b36
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0001
0x659bd0…a9da
6 touches
3 conflicts
0xcce2fd99…a8eb
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x659bd0…a9da
6 touches
3 conflicts
0x7e28e55c…d05c
0x754704…b603
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
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-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity