pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,816,936
← previous block
next block →
recent activity
Analyzing
Block #86,816,936
10 transactions · 8 stateful · 2026-07-10 10:03:51 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,816,936
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#5
0x3f5c179b
#7
0x0f6795d9
#8
0x6a50c3ff
#9
setData
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79ace5b6…8d37
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x65a94b87…2e74
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xec9618aa…0f57
0x34b655…2a6f
4 touches
1 conflict
0xfbc00033…0f93
0x34b655…2a6f
4 touches
1 conflict
0xfbc00033…0f94
0x34b655…2a6f
4 touches
1 conflict
0xd4c992e6…7fa6
0x34b655…2a6f
3 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
0x79ace5b6d1…c68d37
Audit this contract →
← previous block
·
next block →
recent activity