pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,537,513
← previous block
next block →
recent activity
Analyzing
Block #82,537,513
11 transactions · 10 stateful · 2026-06-20 14:05:04 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,537,513
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execPerpOps
#3
execPerpOps
#4
0x5a5d9a99
#5
updateDataFeedsValuesPartial
#6
0x57368ddf
#7
0xe9316489
#8
setData
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdade69ff…a4a4
0x34b655…2a6f
4 touches
1 conflict
0x9e719c7a…df63
0x34b655…2a6f
4 touches
1 conflict
0x6bdb9869…7558
0x34b655…2a6f
4 touches
1 conflict
0x26abe30c…f680
0x34b655…2a6f
2 touches
0 conflicts
0x2de2656d…5bbc
0x34b655…2a6f
2 touches
0 conflicts
0x3d28e1ae…7117
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity