pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,918,076
← previous block
next block →
recent activity
Analyzing
Block #85,918,076
10 transactions · 9 stateful · 2026-07-06 05:57:46 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,918,076
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x0f6795d9
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#5
0x5339c59f
#7
0xed82b078
#8
0x6a4b4452
#9
setData
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2dd2582…6226
0x34b655…2a6f
4 touches
1 conflict
0x0cfc5c41…0986
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x56017f63…8964
0x34b655…2a6f
2 touches
0 conflicts
0x7b3a71df…68d7
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
0xb2dd2582ee…cb6226
Audit this contract →
← previous block
·
next block →
recent activity