pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,266,558
← previous block
next block →
recent activity
Analyzing
Block #82,266,558
12 transactions · 10 stateful · 2026-06-19 07:57:45 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,266,558
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
· blocks 1
#3
0x39435dac
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x5a5d9a99
#7
0x23afbff3
#8
executeBatch
#9
0x3f5c179b
#10
exactInputSingle
#11
setData
#2
transfer
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
0xc4e19ae4…0788
0xe7cd86…c82d
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x499a3b53…08e0
0x065c9d…c394
2 touches
0 conflicts
0xb91c9954…52f7
0x065c9d…c394
2 touches
0 conflicts
0x157dbfb2…4089
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x2d214a61…1f4c
0x34b655…2a6f
2 touches
0 conflicts
0x781f5487…d318
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:
0xe7cd86e1…0fc82d
1 conflict on slot
0xc4e19ae47e…dc0788
Audit this contract →
← previous block
·
next block →
recent activity