pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,758,633
← previous block
next block →
recent activity
Analyzing
Block #87,758,633
11 transactions · 10 stateful · 2026-07-14 19:01:29 UTC
Parallelism
82
/100
Blocked
30
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,758,633
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
· blocks 2
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
· blocks 1
#6
0x6a568801
#7
approve
#8
setData
#10
0xc7e3ec2c
#2
0x98717539
#5
0x5339c59f
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ae859db…2d84
0x34b655…2a6f
4 touches
1 conflict
0xaa643d44…2122
0x34b655…2a6f
4 touches
1 conflict
0xb1d403a3…e612
0x34b655…2a6f
4 touches
1 conflict
0x2f461725…5ab2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x27fe3db5…1a5f
0x40c49f…2af0
4 touches
1 conflict
0xac48464c…69eb
0x40c49f…2af0
4 touches
1 conflict
0x5b145de0…367c
0xc8689a…ee79
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
0x9ae859dbf8…e82d84
Audit this contract →
← previous block
·
next block →
recent activity