pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,752,164
← previous block
next block →
recent activity
Analyzing
Block #94,752,164
12 transactions · 12 stateful · 2026-08-10 10:32:10 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,752,164
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
artefact_keep
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
executeBatch
#6
0xed82b078
#7
0xed82b078
· blocks 1
#9
setData
#10
execOrders
#11
0xc7e3ec2c
#8
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc9cc61f…a0bf
0x065c9d…c394
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0004
0x144a4b…5ba1
2 touches
0 conflicts
0x291f491d…b156
0x34b655…2a6f
2 touches
0 conflicts
0x3111a64f…eb7f
0x34b655…2a6f
2 touches
0 conflicts
0x3915423d…7a97
0x34b655…2a6f
2 touches
0 conflicts
0x3e412550…5c60
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0xfc9cc61f28…50a0bf
Audit this contract →
← previous block
·
next block →
recent activity