← previous blocknext block →recent activity
Analyzing
Block #100,106,668
24 transactions · 23 stateful · 2026-08-29 05:57:21 UTC
Parallelism
75/100
Blocked
61%
Avg conflicts / tx
1.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,106,668 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w08w19w011w113w214w315w216w417w518w119w221w422w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97559ec1…f88c
0x34b655…2a6f
10 touches
10 conflicts
0xa11b60f7…8e8b
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x69411fb3…e36d
0x34b655…2a6f
6 touches
3 conflicts
0x9b334941…fddf
0x1b6862…e19c
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xb52895d6…7dc6
0x34b655…2a6f
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: Perpl
10 conflicts on slot 0x97559ec1df…51f88c
Audit this contract →
← previous block·next block →recent activity