← previous blocknext block →recent activity
Analyzing
Block #106,944,512
23 transactions · 22 stateful · 2026-09-22 04:51:47 UTC
Parallelism
57/100
Blocked
59%
Avg conflicts / tx
2.09
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,944,512 · 23 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
1w02w13w24w35w46w07w08w110w111w212w313w517w718w819w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1660eb0d…e75e
0x34b655…2a6f
16 touches
28 conflicts
0x704a8131…bbe8
0x34b655…2a6f
12 touches
15 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
12 touches
15 conflicts
0x0207f6f2…5d54
0xd32edf…ff58
11 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x14af78bb…aedb
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
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
28 conflicts on slot 0x1660eb0d5b…f5e75e
Audit this contract →
← previous block·next block →recent activity