← previous blocknext block →recent activity
Analyzing
Block #105,841,489
21 transactions · 21 stateful · 2026-09-18 08:18:05 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,841,489 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w010w011w112w213w314w415w516w619w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe40012e6…121d
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xb7ce83b1…2c96
0x34b655…2a6f
12 touches
15 conflicts
0x7b67f6cf…0aab
0x34b655…2a6f
10 touches
10 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x4d42f16e…a6cd
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 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
21 conflicts on slot 0xe40012e6ca…c2121d
Audit this contract →
← previous block·next block →recent activity