← previous blocknext block →recent activity
Analyzing
Block #106,206,914
34 transactions · 31 stateful · 2026-09-19 14:58:25 UTC
Parallelism
59/100
Blocked
55%
Avg conflicts / tx
2.24
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,206,914 · 34 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w09w110w215w218w319w121w423w624w725w826w928w1129w1230w1332w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaaebbec3…8eea
0x34b655…2a6f
22 touches
55 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x4786839b…c29a
0x34b655…2a6f
8 touches
6 conflicts
0xe43b345e…a4e3
0x34b655…2a6f
8 touches
6 conflicts
0x4a974528…2fdb
0x34b655…2a6f
8 touches
6 conflicts
0xfef9b8c0…3db5
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
55 conflicts on slot 0xaaebbec357…778eea
Audit this contract →
← previous block·next block →recent activity