pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,035,590
← previous block
next block →
recent activity
Analyzing
Block #96,035,590
9 transactions · 8 stateful · 2026-08-14 22:23:47 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,035,590
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0x5acec890
· blocks 1
#3
execFwdPositionOpsV2
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOpsV2
#6
setData
#7
refund
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7d08bca…e210
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x200ed648…912f
0x34b655…2a6f
4 touches
1 conflict
0xbb44cedd…c666
0x34b655…2a6f
4 touches
1 conflict
0x2c4dfc9f…110f
0x34b655…2a6f
2 touches
0 conflicts
0x3e3b859f…3654
0x34b655…2a6f
2 touches
0 conflicts
0x4bd46536…17e5
0x34b655…2a6f
2 touches
0 conflicts
0x65744d87…10e6
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
0xc7d08bca4a…77e210
Audit this contract →
← previous block
·
next block →
recent activity