pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,596,248
← previous block
next block →
recent activity
Analyzing
Block #95,596,248
10 transactions · 8 stateful · 2026-08-13 09:32:26 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,596,248
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#3
execOrder
#4
updateDataFeedsValuesPartial
#5
supply
#6
execFwdPositionOps
#7
transfer
#8
setData
#9
execOrders
#2
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xd8b48e27…23a6
0x34b655…2a6f
4 touches
1 conflict
0xe21a94dd…4838
0x34b655…2a6f
3 touches
1 conflict
0x2db15f3e…289d
0x34b655…2a6f
3 touches
1 conflict
0x750fb05c…0e99
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
0x948836ff54…e859ab
Audit this contract →
← previous block
·
next block →
recent activity