← previous blocknext block →recent activity
Analyzing
Block #106,435,526
31 transactions · 30 stateful · 2026-09-20 10:08:59 UTC
Parallelism
55/100
Blocked
53%
Avg conflicts / tx
2.26
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,435,526 · 31 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
1w02w13w14w28w311w412w514w615w716w817w918w1019w1120w1221w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd563f3a1…94b1
0x34b655…2a6f
16 touches
28 conflicts
0xb6ef91c9…73a1
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x228da3f5…c2bf
0x34b655…2a6f
10 touches
10 conflicts
0x172b0de5…980b
0x34b655…2a6f
8 touches
6 conflicts
0xa2df21ed…9f1d
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
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
28 conflicts on slot 0xd563f3a18c…f494b1
Audit this contract →
← previous block·next block →recent activity