pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,459,670
← previous block
next block →
recent activity
Analyzing
Block #85,459,670
10 transactions · 9 stateful · 2026-07-04 03:04:01 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,459,670
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x6a487899
#3
setData
#4
0x0f6795d9
· blocks 1
#5
executeBatch
#6
0xed82b078
#7
0x0f6795d9
#8
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda2ee2e7…968a
0x34b655…2a6f
4 touches
1 conflict
0xdccb9dfe…7a8d
0x34b655…2a6f
4 touches
1 conflict
0xffbcd0b8…3ddb
0x34b655…2a6f
4 touches
1 conflict
0x0af37311…9861
0x34b655…2a6f
4 touches
1 conflict
0x353a3a00…5e0a
0x34b655…2a6f
4 touches
1 conflict
0x37534430…c68b
0x34b655…2a6f
4 touches
1 conflict
0x382b3b57…a546
0x34b655…2a6f
4 touches
1 conflict
0x517d35c7…f359
0x34b655…2a6f
4 touches
1 conflict
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
0xda2ee2e777…e7968a
Audit this contract →
← previous block
·
next block →
recent activity