pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,072,126
← previous block
next block →
recent activity
Analyzing
Block #95,072,126
12 transactions · 11 stateful · 2026-08-11 13:22:35 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,072,126
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execOrder
· blocks 1
#3
execOrder
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
executeBatch
#8
execFwdPositionOps
#9
setData
#10
0xa4d1aa…68c0
#11
0x59558d29
#4
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
2 touches
0 conflicts
0x3c144d40…9554
0x34b655…2a6f
2 touches
0 conflicts
0x40128d8b…37af
0x34b655…2a6f
2 touches
0 conflicts
0x4bc1abab…5874
0x34b655…2a6f
2 touches
0 conflicts
0x55eef346…d185
0x34b655…2a6f
2 touches
0 conflicts
0x734ee320…caae
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
0x4cabb80a0e…7546bf
Audit this contract →
← previous block
·
next block →
recent activity