← previous blocknext block →recent activity
Analyzing
Block #75,846,645
26 transactions · 24 stateful · 2026-05-20 14:28:13 UTC
Parallelism
77/100
Blocked
58%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,846,645 · 26 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
1w02w13w24w35w46w07w38w210w111w012w113w219w222w323w424w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5b10148…e638
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x0e3f6a0f…ea6b
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 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)
10 conflicts on slot 0xd5b1014813…d9e638
Audit this contract →
← previous block·next block →recent activity