← previous blocknext block →recent activity
Analyzing
Block #84,361,023
13 transactions · 11 stateful · 2026-06-29 00:59:10 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,361,023 · 13 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xb89c7e78…0bee
0x1b6862…e19c
4 touches
1 conflict
0x44e0d1db…22f8
0xd32edf…ff58
3 touches
1 conflict
0x29c51ab2…c6e7
0x065c9d…c394
2 touches
0 conflicts
0x3a6769be…0387
0x065c9d…c394
2 touches
0 conflicts
0x58fc94d1…04bb
0x065c9d…c394
2 touches
0 conflicts
0x73b64a36…7512
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)
1 conflict on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity