← previous blocknext block →recent activity
Analyzing
Block #106,328,630
32 transactions · 32 stateful · 2026-09-20 01:11:00 UTC
Parallelism
53/100
Blocked
63%
Avg conflicts / tx
2.53
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,328,630 · 32 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w06w17w08w19w211w212w313w414w515w617w719w820w121w924w126w928w1129w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb654bd89…a83b
0x34b655…2a6f
18 touches
36 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0x5d0915af…762d
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xa182a747…7d1f
0x34b655…2a6f
10 touches
10 conflicts
0x886db264…846e
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
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
36 conflicts on slot 0xb654bd89ad…dba83b
Audit this contract →
← previous block·next block →recent activity