← previous blocknext block →recent activity
Analyzing
Block #100,858,054
18 transactions · 18 stateful · 2026-08-31 21:02:12 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,858,054 · 18 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
1w02w13w04w25w06w07w08w19w210w111w012w116w017w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xce1efe70…2ec8
0x34ae4d…3fc5
4 touches
1 conflict
0x2202504e…fad0
0x34b655…2a6f
4 touches
1 conflict
0x3b9ecd93…6286
0x34b655…2a6f
4 touches
1 conflict
0xa5dd7628…3eb7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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
3 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity