pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,663,565
← previous block
next block →
recent activity
Analyzing
Block #86,663,565
12 transactions · 9 stateful · 2026-07-09 16:59:36 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,663,565
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0d484c28
#2
0x0f6795d9
#3
0x0f6795d9
· blocks 1
#4
0x0f6795d9
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x3f5c179b
#9
transfer
#10
0x0f6795d9
#11
0x6a4fd3f0
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9365e097…ff56
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0xb021166a…acc2
0x000000…012a
2 touches
0 conflicts
0x2c7e7448…9500
0x0000a8…8888
2 touches
0 conflicts
0x2c7e7448…9501
0x0000a8…8888
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
0x9365e0978e…fbff56
Audit this contract →
← previous block
·
next block →
recent activity