← previous blocknext block →recent activity
Analyzing
Block #100,923,391
34 transactions · 26 stateful · 2026-09-01 02:30:51 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.68
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,923,391 · 34 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w39w010w111w412w513w215w317w420w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d4f80a4…bb18
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002d
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001d
0x1b6862…e19c
12 touches
15 conflicts
0x076cca19…81db
0xd32edf…ff58
11 touches
15 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)
15 conflicts on slot 0x7d4f80a446…92bb18
Audit this contract →
← previous block·next block →recent activity