← previous blocknext block →recent activity
Analyzing
Block #78,942,745
11 transactions · 11 stateful · 2026-06-03 22:23:46 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #78,942,745 · 11 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
1w02w03w14w26w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x1bc66ca2…fb4e
0xa6afd3…d132
4 touches
1 conflict
0x565c4328…dec6
0xd32edf…ff58
3 touches
1 conflict
0xe588f517…af00
0x065c9d…c394
2 touches
0 conflicts
0xf3f58353…05be
0x065c9d…c394
2 touches
0 conflicts
0xf66f2e8b…6a77
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity