← previous blocknext block →recent activity
Analyzing
Block #100,628,177
21 transactions · 20 stateful · 2026-08-31 01:45:26 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,628,177 · 21 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
3w04w15w06w17w28w19w013w217w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ad325f5…cc43
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe34ea7da…6882
0x34b655…2a6f
6 touches
3 conflicts
0x28392a33…0f4f
0x34b655…2a6f
4 touches
1 conflict
0x2bf496e1…aae0
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
3 conflicts on slot 0x9ad325f5a1…c3cc43
Audit this contract →
← previous block·next block →recent activity