pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,784,003
← previous block
next block →
recent activity
Analyzing
Block #86,784,003
9 transactions · 8 stateful · 2026-07-10 06:23:50 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,784,003
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5a5d9a99
#2
0x15ea9545
#3
0x0f6795d9
#4
0x0f6795d9
· blocks 2
#5
updateDataFeedsValuesPartial
#8
setData
#6
0x0f6795d9
· blocks 1
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x79ace5b6…8d37
0x34b655…2a6f
4 touches
1 conflict
0xf298c368…a481
0x1efe02…37d6
2 touches
0 conflicts
0x94e7f277…471b
0x34b655…2a6f
2 touches
0 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
2 touches
0 conflicts
0x3230277c…ef39
0xc8689a…ee79
2 touches
0 conflicts
0x002a0f9e…b33b
0xea1b8e…c5ec
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
3 conflicts on slot
0x92385428ad…dc6941
Audit this contract →
← previous block
·
next block →
recent activity