pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,815,508
← previous block
next block →
recent activity
Analyzing
Block #86,815,508
9 transactions · 8 stateful · 2026-07-10 09:54:18 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,815,508
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
· blocks 1
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#7
0x6a50c1c2
#8
setData
#5
0x3f5c179b
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x29a5ecc7…7df7
0x851145…3f07
4 touches
1 conflict
0x0921c970…9f93
0x34b655…2a6f
4 touches
1 conflict
0x3e690221…c7e3
0x34b655…2a6f
4 touches
1 conflict
0x3e690221…c7e4
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8b7af792…9ef0
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xdd75d6f7…dc18
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:
0x851145ea…9f3f07
1 conflict on slot
0x29a5ecc7d5…1f7df7
Audit this contract →
← previous block
·
next block →
recent activity