pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,816,394
← previous block
next block →
recent activity
Analyzing
Block #101,816,394
13 transactions · 12 stateful · 2026-09-04 05:23:47 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,816,394
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x6a9a565a
#3
0x0c7abd22
· blocks 1
#4
updatePrices
#5
updatePrices
#6
0x5acec890
#7
0x5acec890
#8
0x59558d29
#9
conquer
#10
setData
#12
execFwdPositionOpsV2
#11
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ad325f5…cc43
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x03f79551…7bc7
0x34b655…2a6f
2 touches
0 conflicts
0x3cb45e6c…97c0
0x34b655…2a6f
2 touches
0 conflicts
0x3d13406e…eff1
0x34b655…2a6f
2 touches
0 conflicts
0x405567bc…56b0
0x34b655…2a6f
2 touches
0 conflicts
0x4ac80f0d…16d0
0x34b655…2a6f
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
0x9ad325f5a1…c3cc43
Audit this contract →
← previous block
·
next block →
recent activity