← previous blocknext block →recent activity
Analyzing
Block #100,629,148
21 transactions · 19 stateful · 2026-08-31 01:50:19 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,629,148 · 21 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
3w06w18w116w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x565b9117…6375
0x34b655…2a6f
6 touches
3 conflicts
0xb20094ed…0fef
0x34b655…2a6f
4 touches
1 conflict
0xb482658a…e4f5
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x9cdb3cde…bb3b
0x34b655…2a6f
2 touches
0 conflicts
0xb240b520…a88a
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 0x565b911702…c76375
Audit this contract →
← previous block·next block →recent activity