pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,977,873
← previous block
next block →
recent activity
Analyzing
Block #94,977,873
10 transactions · 9 stateful · 2026-08-11 05:27:40 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,977,873
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
0x5acec890
· blocks 1
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#7
transferWithAuthorization
· blocks 1
#9
setData
#6
execFwdPositionOps
#8
transferWithAuthorization
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb0e2447c…17dc
0x754704…b603
4 touches
1 conflict
0x5b350e81…b33f
0x065c9d…c394
2 touches
0 conflicts
0x812bf04f…ba2c
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
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
0x4acbdbcf7f…d0a8c6
Audit this contract →
← previous block
·
next block →
recent activity