pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,061,046
← previous block
next block →
recent activity
Analyzing
Block #94,061,046
10 transactions · 8 stateful · 2026-08-08 00:18:54 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,061,046
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
execFwdPositionOps
· blocks 1
#3
updateDataFeedsValuesPartial
#5
forward
#7
setData
#8
execOrders
#9
0xc7e3ec2c
#4
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42e917f7…ed8c
0x34b655…2a6f
4 touches
1 conflict
0x6651d31f…eff6
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0ed33916…c329
0x34b655…2a6f
2 touches
0 conflicts
0x1b77e6f7…53d7
0x34b655…2a6f
2 touches
0 conflicts
0x2aec4af1…8687
0x34b655…2a6f
2 touches
0 conflicts
0x46ce8421…aeba
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
0x42e917f7fa…e0ed8c
Audit this contract →
← previous block
·
next block →
recent activity