← previous blocknext block →recent activity
Analyzing
Block #82,667,907
31 transactions · 26 stateful · 2026-06-21 04:38:36 UTC
Parallelism
84/100
Blocked
42%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,667,907 · 31 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
1w02w13w24w35w06w17w212w313w014w115w418w426w028w129w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0e4f69d…34e1
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xd03da900…44c8
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
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)
10 conflicts on slot 0xb0e4f69d8e…c534e1
Audit this contract →
← previous block·next block →recent activity