← previous blocknext block →recent activity
Analyzing
Block #102,247,097
25 transactions · 22 stateful · 2026-09-05 17:44:18 UTC
Parallelism
68/100
Blocked
59%
Avg conflicts / tx
1.68
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,247,097 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w26w38w39w314w415w516w617w719w720w424w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001f
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002f
0x1b6862…e19c
16 touches
28 conflicts
0x9256b810…52ce
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x1d1f8e00…3ac7
0xd32edf…ff58
15 touches
28 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)
28 conflicts on slot 0x0000000000…000012
Audit this contract →
← previous block·next block →recent activity