← previous blocknext block →recent activity
Analyzing
Block #106,429,826
21 transactions · 19 stateful · 2026-09-20 09:40:16 UTC
Parallelism
62/100
Blocked
63%
Avg conflicts / tx
1.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,429,826 · 21 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
2w03w14w15w26w07w110w211w312w313w414w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x48716cc0…fe59
0x34b655…2a6f
12 touches
15 conflicts
0x1867b653…e61b
0x34b655…2a6f
10 touches
10 conflicts
0x245a78ab…06b1
0x34b655…2a6f
8 touches
6 conflicts
0x4118bd12…924a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x7752bbe0…fb44
0x34b655…2a6f
8 touches
6 conflicts
0x8d175439…fb79
0x34b655…2a6f
8 touches
6 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 0x48716cc04d…ecfe59
Audit this contract →
← previous block·next block →recent activity