← previous blocknext block →recent activity
Analyzing
Block #84,600,841
8 transactions · 7 stateful · 2026-06-30 03:38:27 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,600,841 · 8 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
1w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xef4096e1…ba67
0x065c9d…c394
4 touches
1 conflict
0xf90cc79d…501b
0x065c9d…c394
4 touches
1 conflict
0xc0d6e1d4…e5e8
0x065c9d…c394
3 touches
1 conflict
0xee122702…053e
0x065c9d…c394
3 touches
1 conflict
0x56785e37…a197
0x065c9d…c394
2 touches
0 conflicts
0x9abcf6b9…3dc7
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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