pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,576,752
← previous block
next block →
recent activity
Analyzing
Block #93,576,752
10 transactions · 8 stateful · 2026-08-06 07:43:24 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,576,752
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
placeAndExecuteMarketBuy
· blocks 1
#7
0x6a743b94
#8
setData
#9
execOrders
#5
batchUpdate
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50e84e6c…287f
0x34b655…2a6f
4 touches
1 conflict
0xb6225cbd…94e1
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0xaff4d265…d411
0x34b655…2a6f
4 touches
1 conflict
0x14bb790b…6c37
0x34b655…2a6f
2 touches
0 conflicts
0x15b47cb9…8bb7
0x34b655…2a6f
2 touches
0 conflicts
0x35b89cd8…5092
0x34b655…2a6f
2 touches
0 conflicts
0x42d5e8f3…5931
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
0x50e84e6ca8…2d287f
Audit this contract →
← previous block
·
next block →
recent activity