← previous blocknext block →recent activity
Analyzing
Block #73,869,507
14 transactions · 12 stateful · 2026-05-11 10:26:34 UTC
Parallelism
43/100
Blocked
58%
Avg conflicts / tx
2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,869,507 · 14 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
1w02w15w27w39w410w511w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x1414f3…5137
16 touches
28 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0fd03d6b…2971
0x1414f3…5137
2 touches
0 conflicts
0x1e21f668…9844
0x1414f3…5137
2 touches
0 conflicts
0x49264b7f…f2e1
0x1414f3…5137
2 touches
0 conflicts
0x90717159…6312
0x1414f3…5137
2 touches
0 conflicts
0xa0d2911b…ecb3
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)
28 conflicts on slot 0x0000000000…000007
Audit this contract →
← previous block·next block →recent activity