← previous blocknext block →recent activity
Analyzing
Block #84,200,564
9 transactions · 7 stateful · 2026-06-28 07:09:49 UTC
Parallelism
56/100
Blocked
43%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,200,564 · 9 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
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb45d9d6…cb86
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0xffc62ba5…0a18
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9d8633b1…b901
0x065c9d…c394
2 touches
0 conflicts
0xad45bd7d…fefc
0x065c9d…c394
2 touches
0 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 0xcb45d9d62a…b1cb86
Audit this contract →
← previous block·next block →recent activity