pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,122,931
← previous block
next block →
recent activity
Analyzing
Block #87,122,931
8 transactions · 7 stateful · 2026-07-11 20:08:46 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,122,931
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 2
#4
0x0f6795d9
#6
setData
#7
0x39435dac
#3
0x0f6795d9
· blocks 1
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0xdd38f4e6…586d
0x34b655…2a6f
4 touches
1 conflict
0x709c2293…6c56
0x34b655…2a6f
4 touches
1 conflict
0x98b248c3…9ea5
0x34b655…2a6f
4 touches
1 conflict
0xa9df6131…bf9a
0x34b655…2a6f
4 touches
1 conflict
0xb8c255af…052c
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
3 conflicts on slot
0x0733be30d6…38112f
Audit this contract →
← previous block
·
next block →
recent activity