pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,196,056
← previous block
next block →
recent activity
Analyzing
Block #76,196,056
12 transactions · 9 stateful · 2026-05-22 05:16:03 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,196,056
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
executeBatch
#7
updateDataFeedsValuesPartial
#8
0xe9316489
· blocks 1
#10
setData
#11
0x115635…4595
#9
0xe9316489
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbc9d8cf…5fde
0x96b79e…d00a
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x04cb7a31…9e1a
0x065c9d…c394
2 touches
0 conflicts
0x17d2b9d3…1a2f
0x065c9d…c394
2 touches
0 conflicts
0x1d47a748…9aa2
0x065c9d…c394
2 touches
0 conflicts
0x81f38805…0337
0x065c9d…c394
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:
0x96b79ef4…d2d00a
1 conflict on slot
0xfbc9d8cfa5…b65fde
Audit this contract →
← previous block
·
next block →
recent activity