pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,673,948
← previous block
next block →
recent activity
Analyzing
Block #85,673,948
10 transactions · 9 stateful · 2026-07-05 02:50:37 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,673,948
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0xa96df62f
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#5
0x3f5c179b
#6
setData
#7
0x39435dac
· blocks 1
#9
0x39435dac
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc8d4ee0…def3
0x34b655…2a6f
4 touches
1 conflict
0x069fcbda…97b5
0x34b655…2a6f
4 touches
1 conflict
0x4c841e83…f270
0x34b655…2a6f
4 touches
1 conflict
0x7c0bdc54…9dde
0x34b655…2a6f
4 touches
1 conflict
0x8656a13f…f95e
0x34b655…2a6f
4 touches
1 conflict
0xc8373a2a…0804
0x34b655…2a6f
4 touches
1 conflict
0xc88e3c8d…710e
0x34b655…2a6f
4 touches
1 conflict
0xd01910c9…9418
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0xdc8d4ee099…56def3
Audit this contract →
← previous block
·
next block →
recent activity