← previous blocknext block →recent activity
Analyzing
Block #84,176,712
12 transactions · 10 stateful · 2026-06-28 04:30:58 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,176,712 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56785e37…a197
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x27467ac9…6523
0x065c9d…c394
2 touches
0 conflicts
0x455fdfa3…9b94
0x065c9d…c394
2 touches
0 conflicts
0x949ff6d2…0210
0x065c9d…c394
2 touches
0 conflicts
0x995addb1…6b26
0x065c9d…c394
2 touches
0 conflicts
0xfd3ed888…8200
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