← previous blocknext block →recent activity
Analyzing
Block #106,923,727
44 transactions · 40 stateful · 2026-09-22 03:07:10 UTC
Parallelism
59/100
Blocked
65%
Avg conflicts / tx
2.18
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #106,923,727 · 44 txs across 18 waves · depth 18
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
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w15w26w07w312w313w414w515w616w717w825w1230w235w141w1542w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcc8f826…7c5f
0x34b655…2a6f
20 touches
45 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
16 touches
28 conflicts
0xdd460daa…6b5b
0x34b655…2a6f
16 touches
28 conflicts
0xccebf5c5…8758
0x34b655…2a6f
16 touches
28 conflicts
0x4996be87…663a
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x1c749e1a…7a46
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
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
45 conflicts on slot 0xfcc8f826d7…5f7c5f
Audit this contract →
← previous block·next block →recent activity