pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,680,433
← previous block
next block →
recent activity
Analyzing
Block #85,680,433
11 transactions · 10 stateful · 2026-07-05 03:33:45 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,680,433
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
· blocks 1
#1
0x39ecce49
· blocks 1
#3
0xab083028
#4
0x0f6795d9
#5
0x0f6795d9
#6
updateDataFeedsValuesPartial
#7
0x6a49d111
#8
setData
#10
0xc7e3ec2c
#2
0x39ecce49
#9
undelegate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
0
w0
1
w0
2
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0003
0x120151…c1d6
4 touches
1 conflict
0x09000000…0007
0x000000…1000
4 touches
1 conflict
0x00000000…0000
0x120151…c1d6
4 touches
1 conflict
0x1a5b83d1…0267
0x73b62f…7777
4 touches
1 conflict
0xbb86cdaf…6a05
0x3bd359…433a
4 touches
1 conflict
0x00000000…0002
0x120151…c1d6
4 touches
1 conflict
0x6cb9514c…c3b3
0x40c49f…2af0
2 touches
0 conflicts
0x213ee207…a151
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:
0x1201512d…cbc1d6
1 conflict on slot
0x0000000000…000003
Audit this contract →
← previous block
·
next block →
recent activity