← previous blocknext block →recent activity
Analyzing
Block #100,851,855
22 transactions · 20 stateful · 2026-08-31 20:31:01 UTC
Parallelism
77/100
Blocked
45%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,851,855 · 22 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
1w02w13w24w310w011w112w213w315w420w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef5a80dc…d544
0x40c49f…2af0
8 touches
6 conflicts
0x2b54cadb…4425
0xd18b7e…414b
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0x892daf6e…48d8
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 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: 0x40c49f17…d22af0
6 conflicts on slot 0xef5a80dcde…65d544
Audit this contract →
← previous block·next block →recent activity