← previous blocknext block →recent activity
Analyzing
Block #84,119,634
19 transactions · 17 stateful · 2026-06-27 22:11:11 UTC
Parallelism
74/100
Blocked
53%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,119,634 · 19 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
1w02w13w24w15w26w07w19w312w413w417w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x73912233…4587
0x1b6862…e19c
8 touches
6 conflicts
0x82d81cf6…f456
0xd32edf…ff58
7 touches
6 conflicts
0x0f6d96f1…10b1
0x065c9d…c394
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
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…000015
Audit this contract →
← previous block·next block →recent activity