← previous blocknext block →recent activity
Analyzing
Block #105,849,986
19 transactions · 19 stateful · 2026-09-18 09:01:00 UTC
Parallelism
32/100
Blocked
63%
Avg conflicts / tx
3.05
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #105,849,986 · 19 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w37w48w59w610w711w812w913w1017w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6caf33e2…c261
0x34b655…2a6f
22 touches
55 conflicts
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0x8c6cec40…ffd5
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x200ac9da…b4db
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xc10b903d…2f54
0x34b655…2a6f
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
55 conflicts on slot 0x6caf33e26f…3dc261
Audit this contract →
← previous block·next block →recent activity