pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,298,549
← previous block
next block →
recent activity
Analyzing
Block #86,298,549
14 transactions · 11 stateful · 2026-07-08 00:17:39 UTC
Parallelism
86
/100
Blocked
18
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,298,549
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x938bf18e
#2
0xab083028
· blocks 1
#3
updatePrices
#4
0x39435dac
#5
0x39435dac
#7
0x5339c59f
#8
forward
#9
updateDataFeedsValuesPartial
#10
0x6a4d979b
#11
setData
#12
0x39435dac
· blocks 1
#6
0x3f5c179b
#13
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
12
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05b1b07a…7a99
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x059114…ac3b
2 touches
0 conflicts
0x00000000…0001
0x059114…ac3b
2 touches
0 conflicts
0x00000000…0002
0x059114…ac3b
2 touches
0 conflicts
0x00000000…0003
0x059114…ac3b
2 touches
0 conflicts
0x0d14a426…d4e1
0x059114…ac3b
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
0x05b1b07aba…747a99
Audit this contract →
← previous block
·
next block →
recent activity