← previous blocknext block →recent activity
Analyzing
Block #106,810,417
28 transactions · 27 stateful · 2026-09-21 17:36:49 UTC
Parallelism
61/100
Blocked
70%
Avg conflicts / tx
2.11
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,810,417 · 28 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w06w17w28w310w311w412w513w614w215w716w125w826w927w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001b
0x1b6862…e19c
16 touches
28 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0xaff4afa8…3f5c
0xd32edf…ff58
15 touches
28 conflicts
0xd228502a…5e76
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x1d9867ad…6d9a
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)
28 conflicts on slot 0x0000000000…000012
Audit this contract →
← previous block·next block →recent activity