← previous blocknext block →recent activity
Analyzing
Block #73,869,440
17 transactions · 15 stateful · 2026-05-11 10:26:07 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.53
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,869,440 · 17 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
1w04w15w06w17w28w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x1414f3…5137
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x7f81fb82…633e
0x065c9d…c394
4 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0xee1914aa…930d
0x065c9d…c394
3 touches
1 conflict
0xf4c41cda…18fb
0x065c9d…c394
3 touches
1 conflict
0x106d721d…45f5
0x065c9d…c394
3 touches
1 conflict
0x2b804638…f2d7
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