pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,281,870
← previous block
next block →
recent activity
Analyzing
Block #86,281,870
11 transactions · 9 stateful · 2026-07-07 22:26:20 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,281,870
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x4d8dc985
#2
0xab083028
#3
0x39435dac
· blocks 1
#5
updateDataFeedsValuesPartial
#6
poke
#7
0x0f6795d9
#8
updateTemporalNumericValuesV1
#9
setData
#10
0x39435dac
#4
0x39435dac
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
0x99701186…1cbf
0x34b655…2a6f
4 touches
1 conflict
0xcc6e2e88…6569
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0xccb8c4ac…aa07
0x34b655…2a6f
4 touches
1 conflict
0x28358a8e…323d
0x34b655…2a6f
4 touches
1 conflict
0x754e4238…cdf3
0x34b655…2a6f
2 touches
0 conflicts
0x9a3068dd…18f0
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
0x997011860a…ad1cbf
Audit this contract →
← previous block
·
next block →
recent activity