← previous blocknext block →recent activity
Analyzing
Block #106,466,404
21 transactions · 21 stateful · 2026-09-20 12:44:25 UTC
Parallelism
71/100
Blocked
57%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,466,404 · 21 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
1w03w04w15w09w110w111w212w213w114w315w417w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x307e2fc2…c8b0
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x4118bd12…924a
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x02fa927d…6468
0x34b655…2a6f
4 touches
1 conflict
0x310a7246…2dcb
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
6 conflicts on slot 0x307e2fc25d…b1c8b0
Audit this contract →
← previous block·next block →recent activity