← previous blocknext block →recent activity
Analyzing
Block #106,463,315
24 transactions · 21 stateful · 2026-09-20 12:28:53 UTC
Parallelism
71/100
Blocked
52%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,463,315 · 24 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
1w02w13w24w35w07w111w214w215w316w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b25f260…c429
0x34b655…2a6f
12 touches
15 conflicts
0x22229acd…2272
0x34b655…2a6f
10 touches
10 conflicts
0xb1927b58…f161
0x34b655…2a6f
10 touches
10 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
10 touches
10 conflicts
0xba4adf08…3e3a
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xed1041a6…f63c
0x34b655…2a6f
6 touches
3 conflicts
0xa60eabc0…9f8c
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
15 conflicts on slot 0x1b25f26097…52c429
Audit this contract →
← previous block·next block →recent activity