← previous blocknext block →recent activity
Analyzing
Block #84,352,692
12 transactions · 11 stateful · 2026-06-29 00:03:33 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,352,692 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56785e37…a197
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x03c325e4…f80f
0x065c9d…c394
2 touches
0 conflicts
0x0f4a848e…739f
0x065c9d…c394
2 touches
0 conflicts
0x5324db1d…b378
0x065c9d…c394
2 touches
0 conflicts
0xd13b963f…f914
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
1 conflict on slot 0x56785e3778…33a197
Audit this contract →
← previous block·next block →recent activity