← previous blocknext block →recent activity
Analyzing
Block #100,873,652
21 transactions · 21 stateful · 2026-08-31 22:20:40 UTC
Parallelism
71/100
Blocked
57%
Avg conflicts / tx
1.48
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,873,652 · 21 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
1w02w15w06w17w29w310w411w012w113w214w315w416w117w520w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1856468…e84f
0x34b655…2a6f
12 touches
15 conflicts
0x0778475b…bd75
0x2a68ba…90c5
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xf0f0caf1…be82
0x065c9d…c394
9 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x9a97b39c…c69c
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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
15 conflicts on slot 0xb185646883…2ae84f
Audit this contract →
← previous block·next block →recent activity