← previous blocknext block →recent activity
Analyzing
Block #100,629,632
16 transactions · 16 stateful · 2026-08-31 01:52:45 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,629,632 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w17w28w110w311w413w214w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c623cfd…b42b
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x1dedc384…ff57
0x851145…3f07
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0xb482658a…e4f5
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x2ce5d13f…f8a9
0x851145…3f07
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
6 conflicts on slot 0x9c623cfd00…4ab42b
Audit this contract →
← previous block·next block →recent activity