← previous blocknext block →recent activity
Analyzing
Block #75,697,333
20 transactions · 17 stateful · 2026-05-19 21:53:04 UTC
Parallelism
85/100
Blocked
29%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,697,333 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w08w19w211w012w116w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x485d2778…aa5e
0x1b6862…e19c
4 touches
1 conflict
0xd68bb69b…1926
0x96b79e…d00a
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
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)
1 conflict on slot 0x485d277847…5daa5e
Audit this contract →
← previous block·next block →recent activity