pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,615,055
← previous block
next block →
recent activity
Analyzing
Block #87,615,055
10 transactions · 10 stateful · 2026-07-14 03:01:10 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,615,055
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 1
#3
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
0x0f6795d9
#7
forward
#8
setData
#9
0x39435dac
#2
0xab083028
· blocks 1
#4
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9c2bb5c…e186
0x40c49f…2af0
4 touches
1 conflict
0xffa7d0a4…b10a
0x40c49f…2af0
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x342fbbca…d443
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x46279ae7…20dd
0x2b46c0…1669
2 touches
0 conflicts
0x53e50026…6d8c
0x2b46c0…1669
2 touches
0 conflicts
0x7f4a8466…f2cc
0x2b46c0…1669
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:
0x40c49f17…d22af0
1 conflict on slot
0xd9c2bb5c48…8fe186
Audit this contract →
← previous block
·
next block →
recent activity