pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,903,061
← previous block
next block →
recent activity
Analyzing
Block #94,903,061
12 transactions · 12 stateful · 2026-08-10 23:11:25 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
#94,903,061
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
placeAndExecuteMarketSell
#3
0x0c7abd22
#4
execOrders
#5
execOrders
#6
updateDataFeedsValuesPartial
#7
0x6a7a5b14
#8
setData
· blocks 1
#10
0x59558d29
· blocks 1
#9
setData
#11
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
2 touches
0 conflicts
0x5261f6ab…9aa1
0x01bff4…1071
2 touches
0 conflicts
0xe78a9e4b…ec2b
0x01bff4…1071
2 touches
0 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
2 touches
0 conflicts
0x32626666…080c
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:
0x33176be2…ede078
1 conflict on slot
0x09106a952c…111467
Audit this contract →
← previous block
·
next block →
recent activity