← previous blocknext block →recent activity
Analyzing
Block #100,228,521
8 transactions · 8 stateful · 2026-08-29 16:10:56 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,228,521 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x005321e0…2e05
0x34b655…2a6f
2 touches
0 conflicts
0x0cdc38ed…c280
0x34b655…2a6f
2 touches
0 conflicts
0x1a69c7c5…09cc
0x34b655…2a6f
2 touches
0 conflicts
0x22162057…c374
0x34b655…2a6f
2 touches
0 conflicts
0x29cd05f5…390c
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity