← previous blocknext block →recent activity
Analyzing
Block #106,424,225
51 transactions · 45 stateful · 2026-09-20 09:12:05 UTC
Parallelism
76/100
Blocked
71%
Avg conflicts / tx
1.86
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,424,225 · 51 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w26w07w08w19w210w311w212w413w514w616w122w324w225w531w134w142w343w446w847w948w1049w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cd9fd28…a158
0x34b655…2a6f
14 touches
21 conflicts
0x3b53436c…2ec3
0x34b655…2a6f
12 touches
15 conflicts
0xd1d2ad0c…9f84
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xfc24540b…6463
0x34b655…2a6f
10 touches
10 conflicts
0x4102cb2a…3b17
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x0c91e576…d4a0
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
21 conflicts on slot 0x7cd9fd286f…a7a158
Audit this contract →
← previous block·next block →recent activity