← previous blocknext block →recent activity
Analyzing
Block #100,925,779
22 transactions · 20 stateful · 2026-09-01 02:42:51 UTC
Parallelism
73/100
Blocked
60%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,925,779 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w07w18w010w111w212w313w414w217w518w519w120w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x34959e1a…ce9c
0x34b655…2a6f
6 touches
3 conflicts
0x3c8d99a5…b937
0x34b655…2a6f
4 touches
1 conflict
0x60b2fe0b…dc32
0x34b655…2a6f
4 touches
1 conflict
0x71fad9ce…c11f
0x34b655…2a6f
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity