← previous blocknext block →recent activity
Analyzing
Block #100,268,168
22 transactions · 21 stateful · 2026-08-29 19:31:56 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,268,168 · 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
1w02w13w04w19w011w112w113w214w318w019w121w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd488e0a9…9bae
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x23529e13…6f25
0x34b655…2a6f
6 touches
3 conflicts
0x2fae69f2…54d5
0x34b655…2a6f
4 touches
1 conflict
0x4786839b…c29a
0x34b655…2a6f
4 touches
1 conflict
0x907f87f3…9efb
0x34b655…2a6f
4 touches
1 conflict
0x953517cb…cdec
0x34b655…2a6f
4 touches
1 conflict
0x990bf0c1…a307
0x34b655…2a6f
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
6 conflicts on slot 0xd488e0a94d…a99bae
Audit this contract →
← previous block·next block →recent activity