pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,182,755
← previous block
next block →
recent activity
Analyzing
Block #85,182,755
10 transactions · 8 stateful · 2026-07-02 20:19:40 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,182,755
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
· blocks 1
#3
0x6a46c854
#5
0x3f5c179b
#6
updateDataFeedsValuesPartial
#7
0x6a46c854
#8
setData
#9
0x39435dac
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x022b49db…a477
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
2 touches
0 conflicts
0x2fd25ab9…95de
0x34b655…2a6f
2 touches
0 conflicts
0x30153288…6d46
0x34b655…2a6f
2 touches
0 conflicts
0x35f31c1b…12ae
0x34b655…2a6f
2 touches
0 conflicts
0x3923cd2c…e6d3
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:
Perpl
1 conflict on slot
0x022b49dbc5…d3a477
Audit this contract →
← previous block
·
next block →
recent activity