← previous blocknext block →recent activity
Analyzing
Block #100,229,415
74 transactions · 51 stateful · 2026-08-29 16:15:26 UTC
Parallelism
80/100
Blocked
76%
Avg conflicts / tx
2.18
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #100,229,415 · 74 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w08w39w112w115w216w318w319w434w135w237w338w439w540w641w742w844w945w1046w1164w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
24 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x443a3e47…f4a4
0x065c9d…c394
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0x0d622e34…0000
0x681e90…ae09
8 touches
6 conflicts
0xb3aa2022…9e09
0x34b655…2a6f
8 touches
6 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
66 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity