pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,122,713
← previous block
next block →
recent activity
Analyzing
Block #87,122,713
8 transactions · 6 stateful · 2026-07-11 20:07:19 UTC
Parallelism
75
/100
Blocked
33
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,122,713
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
aggregate3Value
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 2
#7
setData
#5
0x0f6795d9
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ab0fef9…caef
0x34b655…2a6f
4 touches
1 conflict
0x68edd6ac…8c3c
0x34b655…2a6f
4 touches
1 conflict
0x88e14f13…2975
0x34b655…2a6f
4 touches
1 conflict
0x88e14f13…2976
0x34b655…2a6f
4 touches
1 conflict
0xae10c461…db87
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x1172247d…0022
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
0x4ab0fef975…74caef
Audit this contract →
← previous block
·
next block →
recent activity