pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,626,997
← previous block
next block →
recent activity
Analyzing
Block #86,626,997
10 transactions · 8 stateful · 2026-07-09 12:54:01 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,626,997
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x6a4f9a61
#3
0x5a5d9a99
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x57368ddf
#7
0x0f6795d9
#8
0x6a4f9a61
#9
setData
#4
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc3d4f40…12c9
0x34b655…2a6f
4 touches
1 conflict
0x1321736a…43e3
0x34b655…2a6f
4 touches
1 conflict
0x64a785e4…0110
0x34b655…2a6f
4 touches
1 conflict
0xaba6578d…bd48
0x34b655…2a6f
4 touches
1 conflict
0xd1ec0dfd…ccc0
0xc8689a…ee79
4 touches
1 conflict
0x2556b3c1…0a9e
0x40c49f…2af0
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0xd210dfb5…033a
0x40c49f…2af0
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
0xdc3d4f4025…3c12c9
Audit this contract →
← previous block
·
next block →
recent activity