← previous blocknext block →recent activity
Analyzing
Block #106,931,407
16 transactions · 16 stateful · 2026-09-22 03:45:49 UTC
Parallelism
38/100
Blocked
56%
Avg conflicts / tx
2.06
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,931,407 · 16 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
1w02w13w24w35w47w58w69w710w812w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaf89f45…ced6
0x34b655…2a6f
14 touches
21 conflicts
0x04994ed2…9032
0x34b655…2a6f
12 touches
15 conflicts
0xcaeee6b1…56a0
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x69168e33…6e1f
0x34b655…2a6f
8 touches
6 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
6 touches
3 conflicts
0x650f366d…72ef
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
21 conflicts on slot 0xfaf89f4544…89ced6
Audit this contract →
← previous block·next block →recent activity