pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,528,672
← previous block
next block →
recent activity
Analyzing
Block #95,528,672
10 transactions · 8 stateful · 2026-08-13 03:52:33 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,528,672
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
executeBatch
#7
0x0f6795d9
#8
0x6a7d3ff9
#9
setData
#2
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ee86cb5…db9c
0x99c7a7…8bf0
4 touches
1 conflict
0x9bbb26e8…0d2e
0x99c7a7…8bf0
4 touches
1 conflict
0xa949d556…184c
0x754704…b603
4 touches
1 conflict
0xaad1c5c0…ab91
0x754704…b603
4 touches
1 conflict
0xdc255d21…c377
0x754704…b603
4 touches
1 conflict
0xf7c1f139…3837
0x8f415d…5241
3 touches
1 conflict
0x68faa0b9…14af
0x98dc6e…8633
2 touches
0 conflicts
0x7aada5bb…c8f0
0x98dc6e…8633
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:
0x99c7a72e…c78bf0
1 conflict on slot
0x8ee86cb5fd…29db9c
Audit this contract →
← previous block
·
next block →
recent activity