← previous blocknext block →recent activity
Analyzing
Block #106,916,808
22 transactions · 20 stateful · 2026-09-22 02:32:20 UTC
Parallelism
64/100
Blocked
65%
Avg conflicts / tx
1.18
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,916,808 · 22 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
1w02w13w04w15w26w37w08w09w110w111w212w314w015w416w118w519w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34c48330…703f
0x34b655…2a6f
8 touches
6 conflicts
0x469dac8d…3411
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x3dd71c97…56c6
0x34b655…2a6f
8 touches
6 conflicts
0x6d6c8b37…a8cd
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2130a548…c1de
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
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
6 conflicts on slot 0x34c4833013…14703f
Audit this contract →
← previous block·next block →recent activity