pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,350,677
← previous block
next block →
recent activity
Analyzing
Block #86,350,677
12 transactions · 11 stateful · 2026-07-08 06:05:48 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
#86,350,677
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x785f5745
#4
0x3f5c179b
· blocks 1
#5
0x3f5c179b
#7
forward
#8
0xed82b078
#9
0x6a4de934
#10
setData
#11
0x39435dac
#6
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b405d1c…29a4
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x4a6d03fa…7953
0x851145…3f07
3 touches
1 conflict
0x66d07fd4…fe39
0x851145…3f07
3 touches
1 conflict
0x3c297d95…419d
0x0c65a0…0852
2 touches
0 conflicts
0x490911cc…5fea
0x0c65a0…0852
2 touches
0 conflicts
0x08de772c…8e84
0x2a68ba…90c5
2 touches
0 conflicts
0x1c912a68…3b21
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:
0x851145ea…9f3f07
1 conflict on slot
0x6b405d1c10…7329a4
Audit this contract →
← previous block
·
next block →
recent activity