pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,256,930
← previous block
next block →
recent activity
Analyzing
Block #87,256,930
10 transactions · 10 stateful · 2026-07-12 11:05:28 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,256,930
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 2
#6
0x3f5c179b
#8
setData
#9
0x39435dac
#5
0x0f6795d9
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13ade445…4a0a
0x34b655…2a6f
4 touches
1 conflict
0x256d690b…2bcb
0x34b655…2a6f
4 touches
1 conflict
0x278686dc…698d
0x34b655…2a6f
4 touches
1 conflict
0x29fae93a…bc42
0x34b655…2a6f
4 touches
1 conflict
0x4b389c54…2d3c
0x34b655…2a6f
4 touches
1 conflict
0x51028c5e…235c
0x34b655…2a6f
4 touches
1 conflict
0x6e54dbdd…3231
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
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
0x13ade44529…4d4a0a
Audit this contract →
← previous block
·
next block →
recent activity