pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,758,049
← previous block
next block →
recent activity
Analyzing
Block #87,758,049
11 transactions · 10 stateful · 2026-07-14 18:57:35 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
#87,758,049
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
0x5a5d9a99
· blocks 1
#4
0x5a5d9a99
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x39435dac
#5
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0dd44476…ef40
0x34b655…2a6f
2 touches
0 conflicts
0x293fed86…ed95
0x34b655…2a6f
2 touches
0 conflicts
0x3f798539…99c4
0x34b655…2a6f
2 touches
0 conflicts
0x63e2dc9b…4382
0x34b655…2a6f
2 touches
0 conflicts
0x7ab016af…dae9
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
0x6fe7d366be…a578ff
Audit this contract →
← previous block
·
next block →
recent activity