pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,709,862
← previous block
next block →
recent activity
Analyzing
Block #86,709,862
8 transactions · 6 stateful · 2026-07-09 22:08:32 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,709,862
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
callDiamondWithPermit2
#3
0x0f6795d9
· blocks 1
#4
0x0f6795d9
· blocks 1
#5
updateDataFeedsValuesPartial
#7
setData
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95d63682…276d
0x34b655…2a6f
4 touches
1 conflict
0xae10c461…db87
0x34b655…2a6f
4 touches
1 conflict
0xa9af9157…5a6e
0x34b655…2a6f
4 touches
1 conflict
0xca529dbd…dc62
0x34b655…2a6f
4 touches
1 conflict
0xfbabb02d…af07
0x34b655…2a6f
4 touches
1 conflict
0x5b7b846d…1b95
0x34b655…2a6f
4 touches
1 conflict
0x6b899aa5…a7a6
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
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
0x95d636829f…1f276d
Audit this contract →
← previous block
·
next block →
recent activity