pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,543,775
← previous block
next block →
recent activity
Analyzing
Block #95,543,775
13 transactions · 11 stateful · 2026-08-13 05:08:31 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,543,775
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0x8263f5d9
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x5acec890
· blocks 1
#6
execOrders
#8
execFwdPositionOps
#9
0xed82b078
#10
0x6a7d51c7
#11
setData
#12
0x59558d29
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1526b11f…8b21
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x038b9243…553d
0x34b655…2a6f
2 touches
0 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
2 touches
0 conflicts
0x38a87aeb…21ff
0x34b655…2a6f
2 touches
0 conflicts
0x939cdd56…00c8
0x34b655…2a6f
2 touches
0 conflicts
0xa949d556…184c
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:
Perpl
1 conflict on slot
0x1526b11fec…5a8b21
Audit this contract →
← previous block
·
next block →
recent activity