← previous blocknext block →recent activity
Analyzing
Block #105,760,532
22 transactions · 19 stateful · 2026-09-18 01:29:20 UTC
Parallelism
55/100
Blocked
58%
Avg conflicts / tx
2.18
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,760,532 · 22 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w111w213w314w415w516w617w718w819w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5bb663e0…d8d0
0x34b655…2a6f
20 touches
45 conflicts
0x6771eae2…7014
0x34b655…2a6f
12 touches
15 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
12 touches
15 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
10 touches
10 conflicts
0x6e6a8155…9636
0x34b655…2a6f
10 touches
10 conflicts
0x3180cd66…aaef
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
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
45 conflicts on slot 0x5bb663e0a0…80d8d0
Audit this contract →
← previous block·next block →recent activity