← previous blocknext block →recent activity
Analyzing
Block #77,350,471
38 transactions · 26 stateful · 2026-05-27 13:26:09 UTC
Parallelism
84/100
Blocked
50%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #77,350,471 · 38 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
1w02w13w04w15w26w07w08w09w210w311w412w013w119w220w323w324w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xc51d3663…0f45
0xa6afd3…d132
8 touches
6 conflicts
0xd71a331e…42ea
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c4
0x1b6862…e19c
8 touches
6 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: ShMonad (shMON)
6 conflicts on slot 0x0000000000…00001d
Audit this contract →
← previous block·next block →recent activity