pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,381,719
← previous block
next block →
recent activity
Analyzing
Block #95,381,719
12 transactions · 10 stateful · 2026-08-12 15:32:08 UTC
Parallelism
83
/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,381,719
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x41a8f47c
· blocks 1
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#6
execFwdPositionOps
#7
0x29eed2d3
#8
execFwdPositionOps
#9
transfer
#10
setData
#11
0x59558d29
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x342fbbca…d443
0x40c49f…2af0
4 touches
1 conflict
0xaeb5864c…7679
0x2a68ba…90c5
4 touches
1 conflict
0x22134954…c967
0x40c49f…2af0
3 touches
1 conflict
0x3a921be0…779c
0x2a68ba…90c5
2 touches
0 conflicts
0x5d601639…d720
0x5dd8f3…c69c
2 touches
0 conflicts
0x0b552eae…fbd9
0x754704…b603
2 touches
0 conflicts
0x69c8bf4a…2ed0
0x754704…b603
2 touches
0 conflicts
0x996286b4…54d2
0x754704…b603
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:
0x40c49f17…d22af0
1 conflict on slot
0x342fbbca09…fcd443
Audit this contract →
← previous block
·
next block →
recent activity