← previous blocknext block →recent activity
Analyzing
Block #106,224,571
31 transactions · 30 stateful · 2026-09-19 16:27:17 UTC
Parallelism
55/100
Blocked
77%
Avg conflicts / tx
3.42
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,224,571 · 31 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w19w210w311w214w315w418w319w320w521w622w723w824w926w1027w1128w1229w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67cb0bae…52c3
0x34b655…2a6f
24 touches
66 conflicts
0xecf22f58…5939
0x34b655…2a6f
14 touches
21 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x524f0872…0d12
0x34b655…2a6f
10 touches
10 conflicts
0x742436a7…c4d4
0x34b655…2a6f
10 touches
10 conflicts
0xab981df1…2941
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
66 conflicts on slot 0x67cb0bae57…e552c3
Audit this contract →
← previous block·next block →recent activity