pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,386,425
← previous block
next block →
recent activity
Analyzing
Block #86,386,425
10 transactions · 10 stateful · 2026-07-08 10:04:50 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,386,425
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x6a4e2139
· blocks 1
#4
0x0f6795d9
#5
0x3f5c179b
#6
0x3f5c179b
#7
0x5339c59f
#8
setData
#9
0x39435dac
#3
0x6a4e213a
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xaeb5864c…7679
0x2a68ba…90c5
2 touches
0 conflicts
0x14f6fe51…1c24
0x34b655…2a6f
2 touches
0 conflicts
0x5d4a3441…e31c
0x34b655…2a6f
2 touches
0 conflicts
0x5f251b96…6054
0x34b655…2a6f
2 touches
0 conflicts
0x8de3b6c4…3e82
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity