← previous blocknext block →recent activity
Analyzing
Block #100,159,676
19 transactions · 19 stateful · 2026-08-29 10:24:23 UTC
Parallelism
53/100
Blocked
68%
Avg conflicts / tx
1.37
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,159,676 · 19 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w26w38w49w510w611w712w814w315w816w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20917477…6135
0x34b655…2a6f
12 touches
15 conflicts
0x83f3d320…fb59
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x37699b20…1075
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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: Perpl
15 conflicts on slot 0x2091747705…326135
Audit this contract →
← previous block·next block →recent activity