← previous blocknext block →recent activity
Analyzing
Block #74,774,761
30 transactions · 23 stateful · 2026-05-15 15:03:56 UTC
Parallelism
87/100
Blocked
48%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,774,761 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w310w011w114w017w118w019w120w222w326w027w128w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd53220ed…4736
0x1b6862…e19c
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xc363de7c…b665
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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 0xd53220ed18…174736
Audit this contract →
← previous block·next block →recent activity