pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,277,785
← previous block
next block →
recent activity
Analyzing
Block #94,277,785
12 transactions · 9 stateful · 2026-08-08 18:35:25 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,277,785
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
forward
#6
0xed82b078
#8
updateDataFeedsValuesPartial
#9
0x6a777765
#10
setData
#11
0xc7e3ec2c
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e8ddd73…4dfb
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x07ec3a47…8ec9
0x34b655…2a6f
2 touches
0 conflicts
0x0960ac51…5440
0x34b655…2a6f
2 touches
0 conflicts
0x441923dd…d1a6
0x34b655…2a6f
2 touches
0 conflicts
0x519ff17c…69c2
0x34b655…2a6f
2 touches
0 conflicts
0x5502e1cc…3910
0x34b655…2a6f
2 touches
0 conflicts
0x5b30a6e6…b249
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
0x5e8ddd735e…694dfb
Audit this contract →
← previous block
·
next block →
recent activity