← previous blocknext block →recent activity
Analyzing
Block #84,205,193
13 transactions · 11 stateful · 2026-06-28 07:40:41 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,205,193 · 13 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
1w04w06w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xf33c327f…b162
0x065c9d…c394
4 touches
1 conflict
0x6d215e90…454d
0x065c9d…c394
3 touches
1 conflict
0x99378ec4…0e0e
0x065c9d…c394
3 touches
1 conflict
0x639ed2fa…f476
0xa6afd3…d132
3 touches
1 conflict
0x06e40499…165e
0x69df8a…6292
2 touches
0 conflicts
0x45f562b2…9294
0x69df8a…6292
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity