← previous blocknext block →recent activity
Analyzing
Block #76,112,016
23 transactions · 18 stateful · 2026-05-21 19:56:23 UTC
Parallelism
83/100
Blocked
67%
Avg conflicts / tx
0.87
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,112,016 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w07w18w29w310w011w314w115w016w120w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xec85b41e…7c95
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0x9f71955c…cd0b
0xd32edf…ff58
7 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xffe431af…8faa
0x065c9d…c394
6 touches
3 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…000013
Audit this contract →
← previous block·next block →recent activity