pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,570,333
← previous block
next block →
recent activity
Analyzing
Block #85,570,333
10 transactions · 9 stateful · 2026-07-04 15:20:43 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,570,333
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x5a5d9a99
#3
0x0f6795d9
· blocks 1
#5
0x3f5c179b
#6
0x204ce421
· blocks 1
#8
setData
#9
0x39435dac
#4
0x0f6795d9
#7
0x204ce421
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09500602…94e9
0x34b655…2a6f
4 touches
1 conflict
0x09500602…94ea
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0014
0x2f55a2…8375
4 touches
1 conflict
0x05289bd6…9ab4
0x34b655…2a6f
2 touches
0 conflicts
0x268d9251…1c7f
0x34b655…2a6f
2 touches
0 conflicts
0x3d0454c5…6ab5
0x34b655…2a6f
2 touches
0 conflicts
0x6d02e779…a7f1
0x34b655…2a6f
2 touches
0 conflicts
0x746860d1…e605
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:
Perpl
1 conflict on slot
0x0950060282…6794e9
Audit this contract →
← previous block
·
next block →
recent activity