← previous blocknext block →recent activity
Analyzing
Block #83,956,640
21 transactions · 17 stateful · 2026-06-27 04:05:14 UTC
Parallelism
76/100
Blocked
53%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,956,640 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w19w011w112w114w315w418w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x485d2778…aa5c
0x1b6862…e19c
6 touches
3 conflicts
0x07c77e99…62a9
0xd32edf…ff58
5 touches
3 conflicts
0x82437f64…3f11
0x34b655…2a6f
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)
3 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity