pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,665,801
← previous block
next block →
recent activity
Analyzing
Block #86,665,801
9 transactions · 9 stateful · 2026-07-09 17:14:31 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,665,801
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#6
setData
#7
0x39435dac
#8
0x39435dac
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8058ec4…ebac
0x34b655…2a6f
4 touches
1 conflict
0xf3c7b3c6…c7b6
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0505bae8…b4fb
0x34b655…2a6f
2 touches
0 conflicts
0x06040b44…e244
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94e9
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94ea
0x34b655…2a6f
2 touches
0 conflicts
0x14b926c1…f3d3
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
0xe8058ec456…d4ebac
Audit this contract →
← previous block
·
next block →
recent activity