pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,114,501
← previous block
next block →
recent activity
Analyzing
Block #95,114,501
10 transactions · 10 stateful · 2026-08-11 16:55:46 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,114,501
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execOrder
· blocks 1
#6
0x3f5c179b
#7
0xed82b078
#8
execFwdPositionOps
#9
setData
#2
matchOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9bbb26e8…0d2e
0x99c7a7…8bf0
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xaad1c5c0…ab91
0x754704…b603
4 touches
1 conflict
0xdc255d21…c377
0x754704…b603
4 touches
1 conflict
0xe20cfb89…cd07
0x754704…b603
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x8ee86cb5…db9c
0x99c7a7…8bf0
4 touches
1 conflict
0xfa55cccd…34d6
0x8f415d…5241
3 touches
1 conflict
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
0x9bbb26e8e9…1f0d2e
Audit this contract →
← previous block
·
next block →
recent activity