← previous blocknext block →recent activity
Analyzing
Block #102,358,428
24 transactions · 19 stateful · 2026-09-06 03:08:28 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1.46
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,358,428 · 24 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
1w05w16w27w010w111w212w313w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…001a
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x3e04662b…0da3
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002a
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x2b8d9a56…59d0
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…00001a
Audit this contract →
← previous block·next block →recent activity