← previous blocknext block →recent activity
Analyzing
Block #77,358,900
21 transactions · 17 stateful · 2026-05-27 14:22:19 UTC
Parallelism
62/100
Blocked
53%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #77,358,900 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w59w610w714w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf47a24c4…f77d
0x1414f3…5137
16 touches
28 conflicts
0xe32aecd0…6ef7
0x1414f3…5137
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0xdae18958…32a2
0x1414f3…5137
4 touches
1 conflict
0xb3870dbe…bef3
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xc13fac9b…d2d4
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)
28 conflicts on slot 0xf47a24c4fd…17f77d
Audit this contract →
← previous block·next block →recent activity