← previous blocknext block →recent activity
Analyzing
Block #77,358,901
24 transactions · 20 stateful · 2026-05-27 14:22:20 UTC
Parallelism
75/100
Blocked
55%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #77,358,901 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w38w49w512w117w218w122w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf47a24c4…f77d
0x1414f3…5137
12 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x798969c0…50ce
0x1414f3…5137
6 touches
3 conflicts
0xbab43592…37a6
0xd32edf…ff58
5 touches
3 conflicts
0xdae18958…32a2
0x1414f3…5137
5 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c5
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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)
15 conflicts on slot 0xf47a24c4fd…17f77d
Audit this contract →
← previous block·next block →recent activity