pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,230,366
← previous block
next block →
recent activity
Analyzing
Block #94,230,366
15 transactions · 15 stateful · 2026-08-08 14:34:55 UTC
Parallelism
87
/100
Blocked
7
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,230,366
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execOrders
#3
executeBatch
#4
execFwdPositionOps
· blocks 1
#6
forward
#7
0x6a773f07
#8
setData
#9
execOrders
#10
execOrders
#11
execOrders
#12
execOrders
#13
execOrders
#14
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
0x3371a69b…441e
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x45b4ae9c…dcf4
0x34b655…2a6f
2 touches
0 conflicts
0x4f1ad4b4…e00a
0x34b655…2a6f
2 touches
0 conflicts
0x96249a07…e7fc
0x34b655…2a6f
2 touches
0 conflicts
0xbde524f4…43bf
0x34b655…2a6f
2 touches
0 conflicts
0xc2a783bf…25e3
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
0x3371a69b54…74441e
Audit this contract →
← previous block
·
next block →
recent activity