pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,506,967
← previous block
next block →
recent activity
Analyzing
Block #85,506,967
11 transactions · 11 stateful · 2026-07-04 08:18:51 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,506,967
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1094dc9f
· blocks 1
#3
0x6ad2e98b
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x39435dac
#7
0x0f6795d9
#8
setData
#9
0xc7e3ec2c
#10
0xc7e3ec2c
#2
0xaf5e395a
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99147084…f98d
0x465a0b…3980
4 touches
1 conflict
0x4dd1db39…a995
0x188d58…ea8e
4 touches
1 conflict
0xb0f4dbcb…926a
0x754704…b603
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0xe069120c…952c
0x000000…012a
4 touches
1 conflict
0x4dd1db39…a994
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0004
0x465a0b…3980
4 touches
1 conflict
0x00000000…0005
0x465a0b…3980
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:
0x465a0b35…b53980
1 conflict on slot
0x9914708411…10f98d
Audit this contract →
← previous block
·
next block →
recent activity