pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,528,701
← previous block
next block →
recent activity
Analyzing
Block #84,528,701
11 transactions · 11 stateful · 2026-06-29 19:37:05 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,528,701
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swapWithBackendSignature
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#9
execOrders
#10
execOrders
#2
0xeabbe9d8
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff393f19…4dd2
0x0a3323…0a3c
4 touches
1 conflict
0x00000000…0000
0x0d73bf…be07
4 touches
1 conflict
0x3df7769a…5d17
0x3bd359…433a
4 touches
1 conflict
0x00000000…0002
0x0d73bf…be07
4 touches
1 conflict
0x00000000…0003
0x0d73bf…be07
4 touches
1 conflict
0x00000000…0003
0x04ddf6…7f33
2 touches
0 conflicts
0xcb5be574…fb9f
0x065c9d…c394
2 touches
0 conflicts
0x0ef74796…cd18
0x0a3323…0a3c
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:
0x0a332311…6e0a3c
1 conflict on slot
0xff393f192a…9e4dd2
Audit this contract →
← previous block
·
next block →
recent activity