pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,194,418
← previous block
next block →
recent activity
Analyzing
Block #95,194,418
9 transactions · 8 stateful · 2026-08-11 23:37:44 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
#95,194,418
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
execOrder
· blocks 1
#3
0xb414539a
#4
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
0x927825be
#8
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x87328177…9bfd
0x34b655…2a6f
4 touches
1 conflict
0x25957369…c648
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0ddfdaf2…9e00
0x34b655…2a6f
4 touches
1 conflict
0x3270d9f8…099a
0x34b655…2a6f
2 touches
0 conflicts
0x46ee3c65…4ab8
0x34b655…2a6f
2 touches
0 conflicts
0x5655f5c3…6b75
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
0x873281778c…d89bfd
Audit this contract →
← previous block
·
next block →
recent activity