pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,074,337
← previous block
next block →
recent activity
Analyzing
Block #86,074,337
13 transactions · 12 stateful · 2026-07-06 23:20:56 UTC
Parallelism
77
/100
Blocked
25
%
Avg conflicts / tx
0.31
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,074,337
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updatePrices
#3
execOrders
#4
execOrders
#5
updateDataFeedsValuesPartial
#7
forward
#8
0x6a4c38cf
#9
setData
#10
execOrders
· blocks 2
#6
0x3f5c179b
#11
execOrders
· blocks 1
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
10
w0
11
w1
12
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x006ee1d9…5485
0xa6afd3…d132
4 touches
1 conflict
0x84fb2a36…db89
0x34b655…2a6f
4 touches
1 conflict
0xbcdee322…f454
0xa6afd3…d132
4 touches
1 conflict
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0xfd784183…67bb
0x34b655…2a6f
3 touches
1 conflict
0x8cf3d245…1d0d
0x69df8a…6292
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
3 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity