pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,226,353
← previous block
next block →
recent activity
Analyzing
Block #86,226,353
12 transactions · 11 stateful · 2026-07-07 16:15:38 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,226,353
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
#2
0x0f6795d9
#3
0x3f5c179b
#4
forward
#5
forward
#6
forward
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x39435dac
· blocks 1
#11
0xc7e3ec2c
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2c9f0ac…1942
0x34b655…2a6f
4 touches
1 conflict
0x0c423b46…8777
0x34b655…2a6f
4 touches
1 conflict
0x23253ea8…e0a4
0x34b655…2a6f
4 touches
1 conflict
0x50887223…db7f
0x34b655…2a6f
4 touches
1 conflict
0x57330c5d…9973
0x34b655…2a6f
4 touches
1 conflict
0xa6b89ebb…a66e
0x34b655…2a6f
4 touches
1 conflict
0xb8f817d7…8e60
0x34b655…2a6f
4 touches
1 conflict
0xbb4fd99a…afa6
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
0xe2c9f0ac04…fe1942
Audit this contract →
← previous block
·
next block →
recent activity