pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,856,812
← previous block
next block →
recent activity
Analyzing
Block #93,856,812
11 transactions · 10 stateful · 2026-08-07 07:11:21 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,856,812
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execFwdPositionOps
#3
execFwdPositionOps
#4
execFwdPositionOps
· blocks 1
#6
batchUpdatePrice
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#10
execOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe57232b3…0fbf
0x34b655…2a6f
4 touches
1 conflict
0x04e53004…1b3b
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0e
0x34b655…2a6f
4 touches
1 conflict
0x24b154a6…9864
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x39fb42f2…35f2
0x34b655…2a6f
4 touches
1 conflict
0x72e94d0c…1727
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2db
0x34b655…2a6f
4 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:
Perpl
1 conflict on slot
0xe57232b3f8…130fbf
Audit this contract →
← previous block
·
next block →
recent activity