← previous blocknext block →recent activity
Analyzing
Block #73,869,531
16 transactions · 11 stateful · 2026-05-11 10:26:44 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,869,531 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w19w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x1414f3…5137
10 touches
10 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x413a05c0…fdf4
0x065c9d…c394
2 touches
0 conflicts
0x714357d8…b7b3
0x065c9d…c394
2 touches
0 conflicts
0x72cb6fb0…3e11
0x1414f3…5137
2 touches
0 conflicts
0xa409fc5b…49de
0x1414f3…5137
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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)
10 conflicts on slot 0x0000000000…000007
Audit this contract →
← previous block·next block →recent activity