← previous blocknext block →recent activity
Analyzing
Block #100,635,432
14 transactions · 14 stateful · 2026-08-31 02:21:56 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,635,432 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w09w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x88ecacda…04c9
0xa6afd3…d132
4 touches
1 conflict
0xa0a8ac53…199c
0xa6afd3…d132
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x3c5eae28…c537
0xa6afd3…d132
3 touches
1 conflict
0x8cf3d245…1d0d
0x34ae4d…3fc5
2 touches
0 conflicts
0xad3ef711…4f2b
0x34ae4d…3fc5
2 touches
0 conflicts
0xe2263bea…6a9d
0x34ae4d…3fc5
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
1 conflict on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity