pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,102,647
← previous block
next block →
recent activity
Analyzing
Block #85,102,647
11 transactions · 10 stateful · 2026-07-02 11:24:55 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,102,647
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execute
#5
0x0f6795d9
#6
forward
#7
setData
#8
0x39435dac
#9
0xc7e3ec2c
· blocks 1
#10
0xc7e3ec2c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0xb1c8ea…8888
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x678a8de3…7da5
0x34b655…2a6f
2 touches
0 conflicts
0x81bf2767…e1f4
0x34b655…2a6f
2 touches
0 conflicts
0x8fa63950…f318
0x34b655…2a6f
2 touches
0 conflicts
0xa9988419…9f45
0x34b655…2a6f
2 touches
0 conflicts
0xafd867b7…2b2d
0x34b655…2a6f
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:
0xb1c8ead4…c38888
1 conflict on slot
0x92339d95cd…a80800
Audit this contract →
← previous block
·
next block →
recent activity