pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,517,676
← previous block
next block →
recent activity
Analyzing
Block #87,517,676
11 transactions · 9 stateful · 2026-07-13 16:09:15 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
#87,517,676
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
#4
0x0f6795d9
#5
0x0f6795d9
#6
0x6a550e23
#7
setData
· blocks 1
#9
0x39435dac
#10
0xc7e3ec2c
#8
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x039c2f44…9ac7
0x34b655…2a6f
2 touches
0 conflicts
0x0c25b3bc…5775
0x34b655…2a6f
2 touches
0 conflicts
0x157dbfb2…4089
0x34b655…2a6f
2 touches
0 conflicts
0x20681bc4…c42f
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x2b6a17b1…731d
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:
0x33176be2…ede078
1 conflict on slot
0x09106a952c…111467
Audit this contract →
← previous block
·
next block →
recent activity