pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,504,594
← previous block
next block →
recent activity
Analyzing
Block #85,504,594
12 transactions · 11 stateful · 2026-07-04 08:03:04 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,504,594
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5de3085d
#2
updatePosition
#3
0x3f5c179b
#4
0x0f6795d9
#5
forward
#6
updateDataFeedsValuesPartial
#7
0x204ce421
· blocks 1
#9
0x6a48beb0
#10
setData
#11
0xc7e3ec2c
#8
0x204ce421
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0014
0x2f55a2…8375
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x4c770fe0…b972
0x3bd359…433a
2 touches
0 conflicts
0xa472d565…9fe4
0x3bd359…433a
2 touches
0 conflicts
0xa27fa22d…7dca
0x54cd53…9e7d
2 touches
0 conflicts
0x0d0d16be…8320
0x6657d1…8ccc
2 touches
0 conflicts
0x1584cd40…a598
0x6657d1…8ccc
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:
0x2f55a2e1…f48375
1 conflict on slot
0x0000000000…000014
Audit this contract →
← previous block
·
next block →
recent activity