← previous blocknext block →recent activity
Analyzing
Block #77,357,830
16 transactions · 14 stateful · 2026-05-27 14:15:12 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,357,830 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w09w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xa4e3b3b1…0911
0x2a68ba…90c5
4 touches
1 conflict
0x5dfb2f85…e11a
0x065c9d…c394
4 touches
1 conflict
0x9a8ed5bf…d577
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x9bf064a6…4f04
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
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: ShMonad (shMON)
1 conflict on slot 0xd9f18d9a4a…7f141d
Audit this contract →
← previous block·next block →recent activity