pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,487,795
← previous block
next block →
recent activity
Analyzing
Block #86,487,795
11 transactions · 9 stateful · 2026-07-08 21:22:19 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,487,795
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
multicall
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x0f6795d9
#7
0x6a4ec003
#8
setData
#9
0x39435dac
#10
0xc7e3ec2c
#4
0x000000b2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x7214fb…5853
4 touches
1 conflict
0x1167512f…b162
0x3bd359…433a
4 touches
1 conflict
0x00000000…0003
0x7214fb…5853
4 touches
1 conflict
0x12711b58…80f3
0x384275…7777
4 touches
1 conflict
0x9ba58458…a450
0x11ed3b…2c96
2 touches
0 conflicts
0x00000000…0000
0x2d59fc…cd50
2 touches
0 conflicts
0x00000000…0003
0x2d59fc…cd50
2 touches
0 conflicts
0x00000000…0004
0x2d59fc…cd50
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:
0x7214fb46…875853
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity