pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,245,821
← previous block
next block →
recent activity
Analyzing
Block #86,245,821
13 transactions · 10 stateful · 2026-07-07 18:25:41 UTC
Parallelism
85
/100
Blocked
20
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,245,821
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xd2116f31
#2
updatePrices
· blocks 1
#3
updatePrices
#5
execOrders
· blocks 1
#6
execOrders
#8
updateDataFeedsValuesPartial
#9
0x3f5c179b
#10
0x6a4d451d
#11
setData
#12
execOrders
#4
updatePrices
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x9ff4ca89…6115
0x34b655…2a6f
4 touches
1 conflict
0xd800e635…b1d7
0x34b655…2a6f
4 touches
1 conflict
0x7c67e05d…4d52
0x065c9d…c394
2 touches
0 conflicts
0xe7648170…0b36
0x065c9d…c394
2 touches
0 conflicts
0xed587ea0…8d0e
0x065c9d…c394
2 touches
0 conflicts
0x7f6defda…23fd
0x2a68ba…90c5
2 touches
0 conflicts
0x8876d94c…8435
0x2a68ba…90c5
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:
0x04fdeac2…f747d7
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity