← previous blocknext block →recent activity
Analyzing
Block #79,407,707
30 transactions · 25 stateful · 2026-06-06 02:07:51 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #79,407,707 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w07w18w110w211w012w113w214w315w116w023w425w026w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff176a9…152e
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x1e42621c…605b
0x34b655…2a6f
4 touches
1 conflict
0x89fa3104…8020
0x34b655…2a6f
4 touches
1 conflict
0x93aa4761…99e9
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x9ff176a9ad…67152e
Audit this contract →
← previous block·next block →recent activity