← previous blocknext block →recent activity
Analyzing
Block #100,602,194
61 transactions · 49 stateful · 2026-08-30 23:34:43 UTC
Parallelism
64/100
Blocked
71%
Avg conflicts / tx
2.79
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #100,602,194 · 61 txs across 22 waves · depth 22
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
wave w18
wave w19
wave w20
wave w21
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1019w520w622w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0013
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0015
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…001e
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…002e
0x1b6862…e19c
24 touches
66 conflicts
0xc0f29314…17fd
0x1b6862…e19c
24 touches
66 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
24 touches
66 conflicts
0x19677e17…8f0d
0xd32edf…ff58
23 touches
66 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)
66 conflicts on slot 0x0000000000…000012
Audit this contract →
← previous block·next block →recent activity