← previous blocknext block →recent activity
Analyzing
Block #79,407,125
22 transactions · 18 stateful · 2026-06-06 02:04:00 UTC
Parallelism
73/100
Blocked
44%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #79,407,125 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w48w49w410w518w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bbc0cfb…c2c2
0x1b6862…e19c
8 touches
6 conflicts
0x9ff176a9…152e
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x7699bbde…5b61
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 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: ShMonad (shMON)
6 conflicts on slot 0x2bbc0cfb43…82c2c2
Audit this contract →
← previous block·next block →recent activity