pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,230,573
← previous block
next block →
recent activity
Analyzing
Block #94,230,573
10 transactions · 9 stateful · 2026-08-08 14:35:58 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,230,573
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
execFwdPositionOps
· blocks 1
#4
batchUpdate
#6
updateDataFeedsValuesPartial
#7
0x6a773f46
#8
setData
#9
execOrders
#3
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04994ed2…9032
0x34b655…2a6f
4 touches
1 conflict
0x91c78311…3b17
0x34b655…2a6f
4 touches
1 conflict
0x3b5b6211…f3f4
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x00e21a9f…3583
0x34b655…2a6f
2 touches
0 conflicts
0x0463db49…5d05
0x34b655…2a6f
2 touches
0 conflicts
0x17c5f614…cfc2
0x34b655…2a6f
2 touches
0 conflicts
0x1f90c45d…89c2
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
0x04994ed232…129032
Audit this contract →
← previous block
·
next block →
recent activity