← previous blocknext block →recent activity
Analyzing
Block #106,381,430
27 transactions · 27 stateful · 2026-09-20 05:36:43 UTC
Parallelism
37/100
Blocked
78%
Avg conflicts / tx
5.11
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,381,430 · 27 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w18w213w514w615w716w817w918w1019w1120w1221w1322w1423w1524w1626w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa98e9641…560c
0x34b655…2a6f
24 touches
66 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
24 touches
66 conflicts
0xc644e46e…fcbc
0x34b655…2a6f
12 touches
15 conflicts
0x70986451…c6bd
0x34b655…2a6f
12 touches
15 conflicts
0x8590b692…b267
0x34b655…2a6f
12 touches
15 conflicts
0xd53220ed…4736
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 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
66 conflicts on slot 0xa98e964141…e6560c
Audit this contract →
← previous block·next block →recent activity