pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,873,552
← previous block
next block →
recent activity
Analyzing
Block #85,873,552
9 transactions · 8 stateful · 2026-07-06 01:01:08 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,873,552
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
· blocks 1
#2
execFwdPositionOps
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
0x6a4afecc
#7
setData
#8
0xc7e3ec2c
#3
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09e07591…a43e
0x851145…3f07
4 touches
1 conflict
0x4f5d8f7e…6f56
0x851145…3f07
4 touches
1 conflict
0xc660ab51…886f
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
2 touches
0 conflicts
0x14f6fe51…1c24
0x34b655…2a6f
2 touches
0 conflicts
0x446c9ed6…c25c
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:
0x851145ea…9f3f07
1 conflict on slot
0x09e07591bd…3ba43e
Audit this contract →
← previous block
·
next block →
recent activity