pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,735,999
← previous block
next block →
recent activity
Analyzing
Block #87,735,999
12 transactions · 8 stateful · 2026-07-14 16:30:06 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,735,999
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
depositNative
#2
0x98717539
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
0x3f5c179b
#7
0x3f5c179b
#8
0x0f6795d9
#9
0x07ae8195
#10
setData
#11
0xc7e3ec2c
#3
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e7ebfe…1293
0x34b655…2a6f
4 touches
1 conflict
0x26050074…6967
0x34b655…2a6f
4 touches
1 conflict
0x077d58c3…8ed7
0x34b655…2a6f
4 touches
1 conflict
0x58620f29…db5a
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x9001f549…089d
0x34b655…2a6f
4 touches
1 conflict
0xaf3940ab…8c4c
0x34b655…2a6f
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
0x22e7ebfe72…781293
Audit this contract →
← previous block
·
next block →
recent activity