← previous blocknext block →recent activity
Analyzing
Block #84,282,193
17 transactions · 17 stateful · 2026-06-28 16:13:46 UTC
Parallelism
71/100
Blocked
24%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,282,193 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w211w312w4
- 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
0x56785e37…a197
0x065c9d…c394
4 touches
1 conflict
0x398926d9…cc71
0x065c9d…c394
2 touches
0 conflicts
0x929c3a12…7a8e
0x065c9d…c394
2 touches
0 conflicts
0xca02ebc5…8bba
0x065c9d…c394
2 touches
0 conflicts
0xdd80f66e…2e72
0x065c9d…c394
2 touches
0 conflicts
0xf95c15b9…960f
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity