pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,642,389
← previous block
next block →
recent activity
Analyzing
Block #87,642,389
12 transactions · 8 stateful · 2026-07-14 06:03:53 UTC
Parallelism
83
/100
Blocked
25
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,642,389
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 2
#3
updateDataFeedsValuesPartial
#4
handleOps
#6
forward
#7
0xed82b078
#8
0x6a55d1c1
#9
setData
#10
0x39435dac
#11
0x39435dac
#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
0x369883e3…a449
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e1d87b8…291c
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xe60e9000…c058
0x34b655…2a6f
4 touches
1 conflict
0x83e93c09…a179
0x34b655…2a6f
3 touches
1 conflict
0x158becdc…73ed
0x34b655…2a6f
2 touches
0 conflicts
0x1737ef68…1e55
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
0x369883e38e…11a449
Audit this contract →
← previous block
·
next block →
recent activity