pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,335,193
← previous block
next block →
recent activity
Analyzing
Block #85,335,193
11 transactions · 9 stateful · 2026-07-03 13:14:55 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,335,193
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x719d975a
· blocks 2
#4
updateDataFeedsValuesPartial
#5
0x39435dac
#6
setData
#7
0x0c7abd22
#8
0x0f6795d9
#9
approve
#10
0x1d6381…0bfe
#2
0x9609049f
· blocks 1
#3
0x13572d0b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd06cc746…27e4
0x1001ff…1001
6 touches
3 conflicts
0xd06cc746…27e4
0x91b81b…6d56
6 touches
3 conflicts
0xa159517d…d8d0
0x1001ff…1001
4 touches
1 conflict
0xfe3bddd2…8b48
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x811540…190b
4 touches
1 conflict
0x3d7c0d06…ca8c
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0004
0x811540…190b
4 touches
1 conflict
0xa159517d…d8d0
0x91b81b…6d56
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:
0x1001ff13…0e1001
3 conflicts on slot
0xd06cc7460d…e927e4
Audit this contract →
← previous block
·
next block →
recent activity