← previous blocknext block →recent activity
Analyzing
Block #79,415,768
19 transactions · 16 stateful · 2026-06-06 03:01:37 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
0.68
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #79,415,768 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w07w48w59w613w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6aa624fd…a852
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x0f14fa02…d3cf
0xd32edf…ff58
7 touches
6 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 0x6aa624fd35…14a852
Audit this contract →
← previous block·next block →recent activity