← previous blocknext block →recent activity
Analyzing
Block #84,316,736
7 transactions · 5 stateful · 2026-06-28 20:03:51 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,316,736 · 7 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
1w02w1
- 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
0x537eddb7…986d
0x065c9d…c394
2 touches
0 conflicts
0x8b9d8867…02a5
0x065c9d…c394
2 touches
0 conflicts
0xa633e8d4…51dc
0x065c9d…c394
2 touches
0 conflicts
0xaff9db51…d9e8
0x065c9d…c394
2 touches
0 conflicts
0xcf673367…5f35
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
1 conflict on slot 0x56785e3778…33a197
Audit this contract →
← previous block·next block →recent activity