← previous blocknext block →recent activity
Analyzing
Block #105,849,906
37 transactions · 37 stateful · 2026-09-18 09:00:35 UTC
Parallelism
35/100
Blocked
70%
Avg conflicts / tx
4.08
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #105,849,906 · 37 txs across 24 waves · depth 24
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
wave w19
wave w20
wave w21
wave w22
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w414w517w820w1122w1323w1426w1729w2034w2136w23
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2827ae77…4368
0x34b655…2a6f
24 touches
66 conflicts
0x6caf33e2…c261
0x34b655…2a6f
20 touches
45 conflicts
0x42522e76…2592
0x34b655…2a6f
18 touches
36 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0x43e3decb…be40
0x34b655…2a6f
12 touches
15 conflicts
0x206f4379…e08a
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xe135588e…812f
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 0x2827ae778d…a84368
Audit this contract →
← previous block·next block →recent activity