pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,364,902
← previous block
next block →
recent activity
Analyzing
Block #86,364,902
10 transactions · 8 stateful · 2026-07-08 07:40:41 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
#86,364,902
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#5
0x57368ddf
#6
forward
#7
setData
#8
0x036ddc…2873
#9
0x7ff3cf…23bd
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x87ee379a…cd9e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x14a44e4b…b18d
0x34b655…2a6f
2 touches
0 conflicts
0x19b8b8b8…a37c
0x34b655…2a6f
2 touches
0 conflicts
0x1bb99bba…2911
0x34b655…2a6f
2 touches
0 conflicts
0x2bfff10a…f2e6
0x34b655…2a6f
2 touches
0 conflicts
0x459573ed…fbbe
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
0x87ee379aa1…d8cd9e
Audit this contract →
← previous block
·
next block →
recent activity