pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,103,876
← previous block
next block →
recent activity
Analyzing
Block #85,103,876
8 transactions · 7 stateful · 2026-07-02 11:33:17 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,103,876
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x39435dac
· blocks 1
#7
0xc7e3ec2c
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79b3209b…f766
0x34b655…2a6f
4 touches
1 conflict
0xc6f3c5a3…3faa
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xed59b1cd…8509
0x34b655…2a6f
4 touches
1 conflict
0x4f9529c5…4c96
0x34b655…2a6f
4 touches
1 conflict
0x62b89aef…c9ad
0x34b655…2a6f
4 touches
1 conflict
0xd8fd2add…50fc
0x69df8a…6292
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
0x79b3209b12…57f766
Audit this contract →
← previous block
·
next block →
recent activity