pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,513,803
← previous block
next block →
recent activity
Analyzing
Block #87,513,803
10 transactions · 9 stateful · 2026-07-13 15:43:17 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,513,803
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 2
#3
0x0f6795d9
#4
updateDataFeedsValuesPartial
#6
closeTrade
#7
0x6a55080d
#8
setData
#9
0xc7e3ec2c
#2
0x0f6795d9
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x430b92ea…6f55
0x34b655…2a6f
4 touches
1 conflict
0x430b92ea…6f54
0x34b655…2a6f
4 touches
1 conflict
0x4c8319f0…212b
0x34b655…2a6f
4 touches
1 conflict
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0x59037442…7fd5
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x14c5407b…4a40
0x34b655…2a6f
2 touches
0 conflicts
0x1e9d86f5…53a8
0x34b655…2a6f
2 touches
0 conflicts
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
0x430b92eaca…c76f55
Audit this contract →
← previous block
·
next block →
recent activity