← previous blocknext block →recent activity
Analyzing
Block #106,380,460
48 transactions · 44 stateful · 2026-09-20 05:31:50 UTC
Parallelism
60/100
Blocked
77%
Avg conflicts / tx
2.67
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #106,380,460 · 48 txs across 19 waves · depth 19
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
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w59w410w511w612w719w422w233w236w338w642w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c840894…764a
0x34b655…2a6f
24 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x7462b8f2…6312
0x34b655…2a6f
12 touches
15 conflicts
0xb6fcbbb7…2b31
0x34b655…2a6f
12 touches
15 conflicts
0xca2a4d0d…3a4f
0xd32edf…ff58
11 touches
15 conflicts
0x8d47c9a4…f11c
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x1b25f260…c429
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 0x1c84089465…17764a
Audit this contract →
← previous block·next block →recent activity