pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,281,828
← previous block
next block →
recent activity
Analyzing
Block #87,281,828
8 transactions · 7 stateful · 2026-07-12 13:51:53 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,281,828
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 1
#3
0x0f6795d9
· blocks 1
#6
0xc5a04723
#7
setData
#4
0x0f6795d9
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0feb15e…420b
0x34b655…2a6f
4 touches
1 conflict
0x0960ac51…5440
0x34b655…2a6f
4 touches
1 conflict
0x225bccca…eef7
0x34b655…2a6f
4 touches
1 conflict
0x2c03f397…679c
0x34b655…2a6f
4 touches
1 conflict
0x3413a430…234a
0x34b655…2a6f
4 touches
1 conflict
0x5359bce1…be67
0x34b655…2a6f
4 touches
1 conflict
0x68edd6ac…8c3c
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
0xf0feb15ee5…e9420b
Audit this contract →
← previous block
·
next block →
recent activity