← previous blocknext block →recent activity
Analyzing
Block #105,852,711
25 transactions · 24 stateful · 2026-09-18 09:14:42 UTC
Parallelism
56/100
Blocked
63%
Avg conflicts / tx
1.72
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,852,711 · 25 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w210w011w312w413w514w615w716w817w918w1022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55192654…91fe
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xa9988419…9f45
0x34b655…2a6f
10 touches
10 conflicts
0x8abd0abf…9286
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xe3a467d1…c539
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xeb6b207b…76bd
0xd32edf…ff58
7 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
21 conflicts on slot 0x551926541c…2e91fe
Audit this contract →
← previous block·next block →recent activity