← previous blocknext block →recent activity
Analyzing
Block #84,238,110
17 transactions · 17 stateful · 2026-06-28 11:20:10 UTC
Parallelism
82/100
Blocked
12%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,238,110 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b16149e…7d4d
0x065c9d…c394
6 touches
3 conflicts
0x0fc79a2f…e294
0x065c9d…c394
4 touches
2 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x0eadc03c…626e
0x065c9d…c394
3 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
2 touches
0 conflicts
0x393dfd73…ff57
0x34b655…2a6f
2 touches
0 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
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
3 conflicts on slot 0x0b16149e0d…887d4d
Audit this contract →
← previous block·next block →recent activity