pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,847,604
← previous block
next block →
recent activity
Analyzing
Block #85,847,604
11 transactions · 10 stateful · 2026-07-05 22:08:24 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,847,604
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
#2
0x0f6795d9
#3
0x3f5c179b
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x6a4ad64f
#7
setData
#8
0x39435dac
· blocks 1
#10
0x39435dac
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe59df86b…a00c
0x34b655…2a6f
4 touches
1 conflict
0x3e90ef04…af46
0x34b655…2a6f
4 touches
1 conflict
0x6f58168d…ea24
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
0x34b655…2a6f
4 touches
1 conflict
0x7ae94f4d…f6d6
0x34b655…2a6f
4 touches
1 conflict
0x9092da13…341b
0x34b655…2a6f
4 touches
1 conflict
0x9966da31…0d0f
0x34b655…2a6f
4 touches
1 conflict
0xd4a643ba…138a
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
0xe59df86ba4…a3a00c
Audit this contract →
← previous block
·
next block →
recent activity