← previous blocknext block →recent activity
Analyzing
Block #100,583,787
49 transactions · 37 stateful · 2026-08-30 22:02:07 UTC
Parallelism
59/100
Blocked
70%
Avg conflicts / tx
2.45
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #100,583,787 · 49 txs across 20 waves · depth 20
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w37w48w59w610w727w728w829w333w942w1344w1545w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f28fb99…3d2f
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
18 touches
36 conflicts
0xeb7c9e74…d976
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001e
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002e
0x1b6862…e19c
16 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)
36 conflicts on slot 0x0f28fb99c9…3f3d2f
Audit this contract →
← previous block·next block →recent activity