pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,048,168
← previous block
next block →
recent activity
Analyzing
Block #86,048,168
10 transactions · 10 stateful · 2026-07-06 20:26:25 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,048,168
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
0x3f5c179b
#7
receiveMessage
#8
0xd708c5d8
#9
setData
#2
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf788c790…e66f
0x34b655…2a6f
4 touches
1 conflict
0x4be9812b…48a9
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01fd2f1a…f8f2
0x34b655…2a6f
2 touches
0 conflicts
0x4d236921…feff
0x34b655…2a6f
2 touches
0 conflicts
0x814de043…458c
0x34b655…2a6f
2 touches
0 conflicts
0xa779293b…5e59
0x34b655…2a6f
2 touches
0 conflicts
0xaa226690…99ba
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
1 conflict on slot
0xf788c79025…f8e66f
Audit this contract →
← previous block
·
next block →
recent activity