pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,682,637
← previous block
next block →
recent activity
Analyzing
Block #87,682,637
9 transactions · 9 stateful · 2026-07-14 10:32:49 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,682,637
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xcf27dcc8
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
#7
setData
#8
0x39435dac
#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
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x378c030c…a8a4
0x34b655…2a6f
4 touches
1 conflict
0x378c030c…a8a5
0x34b655…2a6f
4 touches
1 conflict
0xce106f14…913d
0x34b655…2a6f
4 touches
1 conflict
0x40ac0730…2b41
0x34b655…2a6f
3 touches
1 conflict
0x439fef38…da2b
0x34b655…2a6f
3 touches
1 conflict
0xe3a77ce7…0275
0x754704…b603
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
0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block
·
next block →
recent activity