pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,776,685
← previous block
next block →
recent activity
Analyzing
Block #85,776,685
10 transactions · 9 stateful · 2026-07-05 14:15:57 UTC
Parallelism
60
/100
Blocked
33
%
Avg conflicts / tx
0.6
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,776,685
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x957d4ba0
· blocks 3
#5
0xab083028
#6
updateDataFeedsValuesPartial
#7
updatePrices
#8
0x6a4a6795
#9
setData
#2
0x957d4ba0
· blocks 2
#3
0x957d4ba0
· blocks 1
#4
0x957d4ba0
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47d4745e…02bb
0x336ed4…c59c
8 touches
6 conflicts
0x00000000…000a
0x90c374…be45
8 touches
6 conflicts
0x00000000…000b
0x90c374…be45
8 touches
6 conflicts
0xc88f593e…5d93
0x336ed4…c59c
6 touches
3 conflicts
0x79250c04…e936
0x8d1565…6723
4 touches
1 conflict
0x93c58e4d…9b32
0x336ed4…c59c
4 touches
1 conflict
0x10a2bd5d…ad6d
0x8d1565…6723
4 touches
1 conflict
0x4a870d86…79ef
0x336ed4…c59c
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
6 conflicts on slot
0x47d4745e02…9002bb
Audit this contract →
← previous block
·
next block →
recent activity