← previous blocknext block →recent activity
Analyzing
Block #100,984,444
32 transactions · 25 stateful · 2026-09-01 07:37:57 UTC
Parallelism
84/100
Blocked
44%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,984,444 · 32 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w07w18w110w011w116w223w227w328w430w031w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7322fb4a…635e
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
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)
6 conflicts on slot 0x7322fb4afc…ac635e
Audit this contract →
← previous block·next block →recent activity