pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,524,875
← previous block
next block →
recent activity
Analyzing
Block #87,524,875
10 transactions · 7 stateful · 2026-07-13 16:57:54 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,524,875
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x39435dac
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
#7
0x2993270a
#8
setData
#9
0x23ee89…ff1d
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19caa5cc…17c7
0x34b655…2a6f
4 touches
1 conflict
0x3eede796…d745
0x34b655…2a6f
4 touches
1 conflict
0x78b7945b…2113
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xcfe5e2d4…3f3f
0x34b655…2a6f
4 touches
1 conflict
0xf4a27876…b09c
0x34b655…2a6f
4 touches
1 conflict
0xfdd655b8…bf89
0x34b655…2a6f
4 touches
1 conflict
0x4e10224d…58d3
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
0x19caa5cc8d…c217c7
Audit this contract →
← previous block
·
next block →
recent activity