pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,957,778
← previous block
next block →
recent activity
Analyzing
Block #86,957,778
7 transactions · 6 stateful · 2026-07-11 01:45:29 UTC
Parallelism
57
/100
Blocked
33
%
Avg conflicts / tx
0.43
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,957,778
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 2
#6
setData
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7048d42f…288b
0x34b655…2a6f
4 touches
1 conflict
0x1299b030…e115
0x34b655…2a6f
2 touches
0 conflicts
0x4c623175…29e4
0x34b655…2a6f
2 touches
0 conflicts
0x6083af24…a0df
0x34b655…2a6f
2 touches
0 conflicts
0xd1c5aeea…ee0a
0x34b655…2a6f
2 touches
0 conflicts
0xefcaccf2…c083
0x34b655…2a6f
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
0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block
·
next block →
recent activity