pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,584,234
← previous block
next block →
recent activity
Analyzing
Block #83,584,234
11 transactions · 11 stateful · 2026-06-25 10:40:36 UTC
Parallelism
73
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,584,234
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
executePacked
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#6
execFwdPositionOps
#7
0x6a3d061b
#8
setData
#9
execOrders
#10
0xc7e3ec2c
#2
0xed82b078
· blocks 1
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5310ef7…485a
0x40c49f…2af0
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0000
0x25ef1a…5bf1
2 touches
0 conflicts
0x00000000…0002
0x25ef1a…5bf1
2 touches
0 conflicts
0x00000000…00af
0x25ef1a…5bf1
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
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:
0x40c49f17…d22af0
1 conflict on slot
0xf5310ef780…e2485a
Audit this contract →
← previous block
·
next block →
recent activity