pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,983,705
← previous block
next block →
recent activity
Analyzing
Block #85,983,705
16 transactions · 12 stateful · 2026-07-06 13:15:39 UTC
Parallelism
94
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,983,705
· 16 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0xab083028
#2
0x39435dac
#3
0x6df9e92b
#4
0x5bf9264c
#5
0x5bf9264c
#6
0x3f5c179b
#7
0x3f5c179b
#8
0x3f5c179b
#9
forward
#10
0x0f6795d9
#11
updateDataFeedsValuesPartial
#12
updateDataFeedsValuesPartial
#13
setData
#14
0x77057f…2c64
#15
0x49dfc3…c8a3
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xf3eda3f4…e91b
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0000
0x116e7d…d8f1
2 touches
0 conflicts
0x00000000…0002
0x116e7d…d8f1
2 touches
0 conflicts
0x00000000…0003
0x116e7d…d8f1
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.
← previous block
·
next block →
recent activity