pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,674,486
← previous block
next block →
recent activity
Analyzing
Block #85,674,486
10 transactions · 9 stateful · 2026-07-05 02:54:12 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,674,486
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
approve
#2
0x0f6795d9
· blocks 1
#3
0x3f5c179b
#4
0x0c7abd22
#7
updateDataFeedsValuesPartial
#8
0x6a49c7cc
#9
setData
#5
0x0f6795d9
· blocks 1
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0xc0c0abf2…d110
0x34b655…2a6f
4 touches
1 conflict
0x865ea98e…5580
0x34b655…2a6f
4 touches
1 conflict
0x4ee5a465…4ca2
0x34b655…2a6f
4 touches
1 conflict
0x7a51f6c0…1c43
0x34b655…2a6f
4 touches
1 conflict
0x79b15ed1…db9b
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
0xac2a02739b…81721b
Audit this contract →
← previous block
·
next block →
recent activity