← previous blocknext block →recent activity
Analyzing
Block #73,869,006
14 transactions · 12 stateful · 2026-05-11 10:23:14 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,869,006 · 14 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
1w02w13w25w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x1414f3…5137
8 touches
6 conflicts
0xbf25e763…684f
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x776059…1d8d
6 touches
3 conflicts
0x00000000…0001
0x776059…1d8d
6 touches
3 conflicts
0x9b1a47c3…69f8
0xde22b2…7777
6 touches
3 conflicts
0x00000000…0003
0x776059…1d8d
6 touches
3 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
2 touches
0 conflicts
0x908d4442…2c4b
0x34b655…2a6f
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