← previous blocknext block →recent activity
Analyzing
Block #77,355,826
12 transactions · 12 stateful · 2026-05-27 14:01:50 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,355,826 · 12 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
1w04w16w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e0b5ccc…8f29
0x1414f3…5137
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3bac5abd…e0bb
0x065c9d…c394
2 touches
0 conflicts
0x64c31451…5bb2
0x065c9d…c394
2 touches
0 conflicts
0x25400fde…f335
0x1414f3…5137
2 touches
0 conflicts
0x79284dfa…f76e
0x1414f3…5137
2 touches
0 conflicts
0xbc9ca99b…1f23
0x1414f3…5137
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 0x8e0b5ccc7c…a68f29
Audit this contract →
← previous block·next block →recent activity