pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,473,225
← previous block
next block →
recent activity
Analyzing
Block #95,473,225
11 transactions · 10 stateful · 2026-08-12 23:13:40 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,473,225
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0x5acec890
#3
0x5acec890
#4
0x222d4ad6
#5
execFwdPositionOps
· blocks 1
#6
executeBatch
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x59558d29
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24b08f9c…e594
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
2 touches
0 conflicts
0x70e3da66…674a
0x34b655…2a6f
2 touches
0 conflicts
0x84d74093…7808
0x34b655…2a6f
2 touches
0 conflicts
0x8d4c0bb9…ccd3
0x34b655…2a6f
2 touches
0 conflicts
0xa5ab7b8a…c97b
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
0x24b08f9c98…6ae594
Audit this contract →
← previous block
·
next block →
recent activity