← previous blocknext block →recent activity
Analyzing
Block #80,249,403
38 transactions · 31 stateful · 2026-06-09 23:51:34 UTC
Parallelism
79/100
Blocked
58%
Avg conflicts / tx
1.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #80,249,403 · 38 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w19w213w314w415w516w617w718w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd996735f…8735
0x1b6862…e19c
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
10 touches
10 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)
10 conflicts on slot 0xd996735f25…4f8735
Audit this contract →
← previous block·next block →recent activity