← previous blocknext block →recent activity
Analyzing
Block #102,210,103
40 transactions · 39 stateful · 2026-09-05 14:36:55 UTC
Parallelism
55/100
Blocked
69%
Avg conflicts / tx
4.33
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #102,210,103 · 40 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w05w16w27w38w49w510w611w712w813w914w1015w1116w1217w1318w1419w1520w1621w1726w237w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…001f
0x1b6862…e19c
36 touches
153 conflicts
0x00000000…0012
0x1b6862…e19c
36 touches
153 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
36 touches
153 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
36 touches
153 conflicts
0x07e0b659…931b
0xd32edf…ff58
35 touches
153 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 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)
153 conflicts on slot 0x0000000000…00001f
Audit this contract →
← previous block·next block →recent activity