← previous blocknext block →recent activity
Analyzing
Block #106,954,371
26 transactions · 25 stateful · 2026-09-22 05:41:25 UTC
Parallelism
62/100
Blocked
64%
Avg conflicts / tx
2.23
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,954,371 · 26 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
1w02w13w24w35w46w311w412w513w314w615w717w420w821w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x351fcb8b…49ab
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xfa324e43…8899
0x1b6862…e19c
10 touches
10 conflicts
0x01ad5dd0…11a1
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
36 conflicts on slot 0x351fcb8b6b…2349ab
Audit this contract →
← previous block·next block →recent activity