pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,853,530
← previous block
next block →
recent activity
Analyzing
Block #93,853,530
12 transactions · 12 stateful · 2026-08-07 06:54:51 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,853,530
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
approve
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
metacall
#6
0x3f5c179b
#7
execFwdPositionOps
#8
execFwdPositionOps
· blocks 1
#10
setData
#9
execFwdPositionOps
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w0
9
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdc1731c…b91a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0001
0x2da28f…75e8
2 touches
0 conflicts
0x00000000…0003
0x2da28f…75e8
2 touches
0 conflicts
0xf334fe53…11d8
0x2da28f…75e8
2 touches
0 conflicts
0x1eb0fab5…3517
0x34b655…2a6f
2 touches
0 conflicts
0x673891f1…bf47
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
0xcdc1731c6b…b6b91a
Audit this contract →
← previous block
·
next block →
recent activity