pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,215,050
← previous block
next block →
recent activity
Analyzing
Block #106,215,050
14 transactions · 13 stateful · 2026-09-19 15:39:22 UTC
Parallelism
86
/100
Blocked
15
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,215,050
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updatePrices
#3
0xab083028
#4
0xab083028
#5
0x5acec890
#6
0x5acec890
#7
0x5acec890
· blocks 1
#8
execOrders
· blocks 1
#10
sweepNative
#11
transferWithAuthorization
#12
setData
#9
execOrders
#13
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w0
9
w1
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x64141a92…64fd
0x34b655…2a6f
4 touches
1 conflict
0xc12ec6f1…9467
0x34b655…2a6f
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x00532bf5…5711
0x754704…b603
2 touches
0 conflicts
0x0eff0903…8165
0x754704…b603
2 touches
0 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
1 conflict on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity