pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,334,814
← previous block
next block →
recent activity
Analyzing
Block #84,334,814
11 transactions · 11 stateful · 2026-06-28 22:04:21 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,334,814
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x98717539
#4
artefact_keep
#5
execFwdPositionOps
· blocks 1
#6
forward
#7
0xed82b078
· blocks 1
#10
setData
#8
0xed82b078
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w0
8
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2ed607d…4d45
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x29daa333…2c3d
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
2 touches
0 conflicts
0x6f132c01…cdcd
0x34b655…2a6f
2 touches
0 conflicts
0x826cce18…251c
0x34b655…2a6f
2 touches
0 conflicts
0x8295c19b…46fa
0x34b655…2a6f
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
0xa2ed607df9…934d45
Audit this contract →
← previous block
·
next block →
recent activity