← previous blocknext block →recent activity
Analyzing
Block #100,752,178
70 transactions · 37 stateful · 2026-08-31 12:09:11 UTC
Parallelism
89/100
Blocked
65%
Avg conflicts / tx
1.03
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,752,178 · 70 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w28w014w115w216w317w418w521w332w434w540w644w345w748w169w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
16 touches
28 conflicts
0xaad6be10…0801
0x2a68ba…90c5
14 touches
21 conflicts
0x3f81bcfb…2905
0x40c49f…2af0
10 touches
10 conflicts
0x065ff70b…356d
0x40c49f…2af0
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0xb718454d…a6bc
0xd32edf…ff58
7 touches
6 conflicts
0x7f4a8466…f2cc
0x34ae4d…3fc5
6 touches
3 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: 0xf5b5f7f8…a36d70
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity