pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,133,362
← previous block
next block →
recent activity
Analyzing
Block #85,133,362
13 transactions · 10 stateful · 2026-07-02 14:50:38 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,133,362
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1094dc9f
#2
0xab083028
#3
updatePrices
#4
updatePrices
#5
0x6c05cd2b
#6
0x5a5d9a99
· blocks 1
#8
updateDataFeedsValuesPartial
#9
0x0f6795d9
#10
transfer
#11
setData
#12
0x39435dac
#7
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x064fb5…6207
2 touches
0 conflicts
0x00000000…0001
0x064fb5…6207
2 touches
0 conflicts
0x00000000…0008
0x064fb5…6207
2 touches
0 conflicts
0x38aa1898…fdf5
0x11ed3b…2c96
2 touches
0 conflicts
0xfd4df3d8…23fe
0x11ed3b…2c96
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
0xfaef08b108…f90696
Audit this contract →
← previous block
·
next block →
recent activity