pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,796,065
← previous block
next block →
recent activity
Analyzing
Block #85,796,065
8 transactions · 4 stateful · 2026-07-05 16:25:04 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,796,065
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactInputSingle
#2
updateDataFeedsValuesPartial
#3
0x5339c59f
#4
setData
#5
0x9b0fd8…d1c3
#6
0x39435dac
· blocks 1
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53cccb07…d7f0
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x03806aed…3200
0x065c9d…c394
2 touches
0 conflicts
0x16de8c6d…31c6
0x065c9d…c394
2 touches
0 conflicts
0x2557a216…1a71
0x065c9d…c394
2 touches
0 conflicts
0x4bc3aee7…9aec
0x065c9d…c394
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
0x53cccb0751…4fd7f0
Audit this contract →
← previous block
·
next block →
recent activity