pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,330,607
← previous block
next block →
recent activity
Analyzing
Block #84,330,607
11 transactions · 8 stateful · 2026-06-28 21:36:22 UTC
Parallelism
73
/100
Blocked
25
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,330,607
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
executeBatch
#3
execFwdPositionOps
· blocks 2
#4
updateDataFeedsValuesPartial
#5
0x6a41944e
#6
setData
#7
0x1f78a0…158c
#8
0xda14f5…41be
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
9
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b2dce58…2f1d
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xa45116ed…5331
0x34b655…2a6f
4 touches
1 conflict
0xbb79f6c1…979b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xecf5834b…70b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
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
3 conflicts on slot
0x2b2dce5827…4f2f1d
Audit this contract →
← previous block
·
next block →
recent activity