← previous blocknext block →recent activity
Analyzing
Block #83,865,826
9 transactions · 9 stateful · 2026-06-26 17:59:56 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,865,826 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21bf
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x87a1698c…1c1d
0xd32edf…ff58
3 touches
1 conflict
0x7cc44b1b…e8cb
0x065c9d…c394
2 touches
0 conflicts
0x905c2535…405a
0x065c9d…c394
2 touches
0 conflicts
0xc2c5136e…9f6d
0x065c9d…c394
2 touches
0 conflicts
0x00f7e3b7…e015
0x188d58…ea8e
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)
1 conflict on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity