← previous blocknext block →recent activity
Analyzing
Block #73,869,417
11 transactions · 8 stateful · 2026-05-11 10:25:58 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,869,417 · 11 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
1w02w13w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x1414f3…5137
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2b804638…f2d7
0x065c9d…c394
2 touches
0 conflicts
0x33d611dc…2b65
0x065c9d…c394
2 touches
0 conflicts
0x35be7621…b8d2
0x065c9d…c394
2 touches
0 conflicts
0x3caff45b…64e7
0x065c9d…c394
2 touches
0 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: Monad Mogs (MOGS)
6 conflicts on slot 0x0000000000…000007
Audit this contract →
← previous block·next block →recent activity