pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,568,818
← previous block
next block →
recent activity
Analyzing
Block #95,568,818
13 transactions · 10 stateful · 2026-08-13 07:14:28 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,568,818
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#2
updateDataFeedsValuesPartial
#3
execOrders
#5
setData
#6
execOrders
#7
execOrders
#8
execOrders
#9
execOrders
#10
execOrders
#11
execOrders
#12
0x61d59c2d
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7947fe4a…1519
0x34b655…2a6f
4 touches
1 conflict
0x8ec95f2b…f4d7
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x22c6ecc6…c70d
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x320701d5…f9f3
0x34b655…2a6f
2 touches
0 conflicts
0x3dfb933f…7999
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
0x7947fe4a57…dc1519
Audit this contract →
← previous block
·
next block →
recent activity