← previous blocknext block →recent activity
Analyzing
Block #77,358,993
32 transactions · 23 stateful · 2026-05-27 14:22:56 UTC
Parallelism
66/100
Blocked
61%
Avg conflicts / tx
1.84
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #77,358,993 · 32 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w59w610w711w812w913w1026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5de99b9…676e
0x1414f3…5137
22 touches
55 conflicts
0x1663ef04…fadc
0x1414f3…5137
9 touches
10 conflicts
0xfa915fc0…4782
0x1414f3…5137
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
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)
55 conflicts on slot 0xa5de99b9e6…af676e
Audit this contract →
← previous block·next block →recent activity