pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,992,526
← previous block
next block →
recent activity
Analyzing
Block #85,992,526
12 transactions · 11 stateful · 2026-07-06 14:14:39 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,992,526
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x0f6795d9
#3
0x0f6795d9
· blocks 1
#4
0x3f5c179b
#5
forward
#6
0x0f6795d9
#7
updateDataFeedsValuesPartial
#8
0x4a01e1…2856
#9
setData
#11
0xc7e3ec2c
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c8a3a66…2a9c
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x23253ea8…e0a4
0x34b655…2a6f
2 touches
0 conflicts
0x2f358e74…1022
0x34b655…2a6f
2 touches
0 conflicts
0x43e0a706…ded6
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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
0x1c8a3a666c…0c2a9c
Audit this contract →
← previous block
·
next block →
recent activity