pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,369,153
← previous block
next block →
recent activity
Analyzing
Block #97,369,153
13 transactions · 12 stateful · 2026-08-19 14:33:40 UTC
Parallelism
77
/100
Blocked
25
%
Avg conflicts / tx
0.31
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,369,153
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
commitVerification
#2
0xab083028
· blocks 1
#4
execOrder
· blocks 2
#7
redeem
#8
updateDataFeedsValuesPartial
#9
executeBatch
#10
forward
#11
setData
#12
execOrders
#3
0x8263f5d9
#5
execOrder
· blocks 1
#6
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x2d8487d0…24c6
0x34b655…2a6f
4 touches
1 conflict
0x3c6109c3…1ea7
0x34b655…2a6f
4 touches
1 conflict
0x54b46054…b706
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity