← previous blocknext block →recent activity
Analyzing
Block #106,953,413
25 transactions · 25 stateful · 2026-09-22 05:36:35 UTC
Parallelism
72/100
Blocked
68%
Avg conflicts / tx
1.8
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,953,413 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w08w19w211w212w313w319w420w523w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x82c4cda4…0ebf
0x34b655…2a6f
12 touches
15 conflicts
0x1b075fe1…d840
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x64e1f0ce…715b
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x67287ef9…2d07
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0x82c4cda410…4b0ebf
Audit this contract →
← previous block·next block →recent activity