← previous blocknext block →recent activity
Analyzing
Block #105,922,269
21 transactions · 20 stateful · 2026-09-18 15:05:40 UTC
Parallelism
62/100
Blocked
50%
Avg conflicts / tx
1.24
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,922,269 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w08w010w112w213w014w115w317w418w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x375b6201…9c1e
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0x8f738079…ec1d
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x3018a378…d7bb
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
6 conflicts on slot 0x375b620113…4b9c1e
Audit this contract →
← previous block·next block →recent activity