pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,656,187
← previous block
next block →
recent activity
Analyzing
Block #83,656,187
12 transactions · 12 stateful · 2026-06-25 18:41:10 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,656,187
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
0x98717539
· blocks 1
#5
0x5a5d9a99
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x0f6795d9
#9
setData
#10
0x39435dac
#11
0xc7e3ec2c
#4
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76477ddf…b8f8
0xc8689a…ee79
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x3b9a46bd…a7cd
0x065c9d…c394
2 touches
0 conflicts
0xb563ae77…3576
0x065c9d…c394
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x21f3627e…adb0
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: Settlement / Helper
1 conflict on slot
0x76477ddf28…1bb8f8
Audit this contract →
← previous block
·
next block →
recent activity