← previous blocknext block →recent activity
Analyzing
Block #73,869,389
10 transactions · 9 stateful · 2026-05-11 10:25:47 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,869,389 · 10 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
1w05w16w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x1414f3…5137
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x22ef1e0b…b650
0x065c9d…c394
2 touches
0 conflicts
0x27aceec2…e0bd
0x065c9d…c394
2 touches
0 conflicts
0x2ad7f58c…03c2
0x065c9d…c394
2 touches
0 conflicts
0x5359bb9e…6630
0x065c9d…c394
2 touches
0 conflicts
0x89c956c0…ecac
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)
3 conflicts on slot 0x0000000000…000007
Audit this contract →
← previous block·next block →recent activity