← previous blocknext block →recent activity
Analyzing
Block #73,807,780
18 transactions · 13 stateful · 2026-05-11 03:35:23 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,807,780 · 18 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
1w02w13w24w38w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3bd55803…5d4f
0x1b6862…e19c
6 touches
3 conflicts
0x8a35acfb…d1ae
0x8d66a4…3095
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xc983972d…8580
0x065c9d…c394
5 touches
3 conflicts
0xae69c125…2379
0x2a68ba…90c5
5 touches
3 conflicts
0x7ecdf824…35df
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
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)
3 conflicts on slot 0x3bd558039d…705d4f
Audit this contract →
← previous block·next block →recent activity