pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,184,660
← previous block
next block →
recent activity
Analyzing
Block #85,184,660
11 transactions · 8 stateful · 2026-07-02 20:32:20 UTC
Parallelism
82
/100
Blocked
25
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,184,660
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x957d4ba0
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x0f6795d9
#9
0x6a46cb4c
#10
setData
#2
0x0c7abd22
#4
0x957d4ba0
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc88f593e…5d93
0x336ed4…c59c
4 touches
1 conflict
0x00000000…000b
0x90c374…be45
4 touches
1 conflict
0x00000000…000a
0x90c374…be45
4 touches
1 conflict
0x79250c04…e936
0x8d1565…6723
4 touches
1 conflict
0x10a2bd5d…ad6d
0x8d1565…6723
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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:
0x336ed437…cfc59c
1 conflict on slot
0xc88f593e3b…e65d93
Audit this contract →
← previous block
·
next block →
recent activity