pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,978,658
← previous block
next block →
recent activity
Analyzing
Block #86,978,658
10 transactions · 10 stateful · 2026-07-11 04:04:59 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,978,658
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x0c9bed1a
· blocks 1
#6
0x0f6795d9
#8
0x0f6795d9
#9
setData
#7
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x5b09b6…a607
4 touches
1 conflict
0x6002379f…9f90
0x5b09b6…a607
4 touches
1 conflict
0x6002379f…9f91
0x5b09b6…a607
4 touches
1 conflict
0x6002379f…9f94
0x5b09b6…a607
4 touches
1 conflict
0xad676684…c58b
0x754704…b603
4 touches
1 conflict
0x152f8e3d…3da0
0x34b655…2a6f
2 touches
0 conflicts
0x1ba5d36c…9336
0x34b655…2a6f
2 touches
0 conflicts
0x2029b74e…c206
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:
0x5b09b68b…c6a607
1 conflict on slot
0x0000000000…000006
Audit this contract →
← previous block
·
next block →
recent activity