pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,351,864
← previous block
next block →
recent activity
Analyzing
Block #86,351,864
12 transactions · 10 stateful · 2026-07-08 06:13:43 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,351,864
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0xab083028
#3
updatePrices
#4
0x50a0b275
· blocks 1
#6
0x0f6795d9
· blocks 1
#7
updateDataFeedsValuesPartial
#9
0x5339c59f
#10
setData
#11
0x39435dac
#5
0x62be7533
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1af7d74…7622
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0x398e3d…298c
4 touches
1 conflict
0x00000000…0002
0x398e3d…298c
4 touches
1 conflict
0x00000000…0004
0x398e3d…298c
4 touches
1 conflict
0x00000000…000c
0x398e3d…298c
4 touches
1 conflict
0x9ef62133…9b47
0x3bd359…433a
4 touches
1 conflict
0xf6802cf0…344f
0x000000…012a
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
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
0xe1af7d7426…a57622
Audit this contract →
← previous block
·
next block →
recent activity