← previous blocknext block →recent activity
Analyzing
Block #106,565,124
64 transactions · 45 stateful · 2026-09-20 21:01:15 UTC
Parallelism
75/100
Blocked
67%
Avg conflicts / tx
2.13
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,565,124 · 64 txs across 16 waves · depth 16
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
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w08w110w212w013w115w016w117w218w327w430w536w637w738w842w344w848w149w1150w1252w1353w1455w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xddd20e39…d524
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0xea02471d…1542
0x34b655…2a6f
14 touches
21 conflicts
0x3b8d7efd…a779
0x34b655…2a6f
12 touches
15 conflicts
0x5a541bec…80fc
0x34b655…2a6f
12 touches
15 conflicts
0x5f13dc38…5584
0x34b655…2a6f
12 touches
15 conflicts
0x8b9390da…3820
0x34b655…2a6f
12 touches
15 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
45 conflicts on slot 0xddd20e3989…a2d524
Audit this contract →
← previous block·next block →recent activity