← previous blocknext block →recent activity
Analyzing
Block #100,611,125
26 transactions · 25 stateful · 2026-08-31 00:19:39 UTC
Parallelism
77/100
Blocked
56%
Avg conflicts / tx
1.15
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,611,125 · 26 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
1w02w13w04w06w07w18w19w012w113w214w315w017w118w119w220w321w123w324w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x556a9a7a…b0ae
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf65c9ad4…88f7
0x34b655…2a6f
8 touches
6 conflicts
0xf9b327ff…578e
0x34b655…2a6f
8 touches
6 conflicts
0x08731834…6415
0x34b655…2a6f
6 touches
3 conflicts
0x5a548af5…0eb0
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity