pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,248,461
← previous block
next block →
recent activity
Analyzing
Block #86,248,461
10 transactions · 8 stateful · 2026-07-07 18:43:22 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,248,461
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe3a3c9cc
#2
0x0d484c28
#3
updateDataFeedsValuesPartial
#4
compound
#5
0x39435dac
· blocks 1
#7
setData
#8
0x39435dac
#9
0xc7e3ec2c
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbabe821d…939b
0x34b655…2a6f
4 touches
1 conflict
0xc9b54d67…3f60
0x34b655…2a6f
4 touches
1 conflict
0xd7897fb0…45e9
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0xf0c9bd80…2467
0x34b655…2a6f
4 touches
1 conflict
0x141c490e…8343
0x34b655…2a6f
4 touches
1 conflict
0x146c718c…8a22
0x34b655…2a6f
4 touches
1 conflict
0x181732de…9796
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
0xbabe821d83…a1939b
Audit this contract →
← previous block
·
next block →
recent activity