pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,355,788
← previous block
next block →
recent activity
Analyzing
Block #87,355,788
9 transactions · 8 stateful · 2026-07-12 22:06:26 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,355,788
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#6
0xbf82f22b
#7
setData
#5
0x0f6795d9
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x78255c70…2733
0x34b655…2a6f
4 touches
1 conflict
0xc5570577…8bf0
0x34b655…2a6f
4 touches
1 conflict
0xde9bb8b7…ac39
0x34b655…2a6f
4 touches
1 conflict
0xf4ff6152…dac9
0x34b655…2a6f
4 touches
1 conflict
0xfd02114c…64e7
0x34b655…2a6f
4 touches
1 conflict
0x78255c70…2734
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5b960f5f…607e
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
0x78255c70bd…2a2733
Audit this contract →
← previous block
·
next block →
recent activity