← previous blocknext block →recent activity
Analyzing
Block #84,026,520
30 transactions · 24 stateful · 2026-06-27 11:50:51 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,026,520 · 30 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
1w02w13w24w15w36w410w013w121w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17a7f697…dcb4
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001b
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0xfc632089…8d2e
0xd32edf…ff58
9 touches
10 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 0x17a7f69751…9bdcb4
Audit this contract →
← previous block·next block →recent activity