pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,145,297
← previous block
next block →
recent activity
Analyzing
Block #85,145,297
10 transactions · 10 stateful · 2026-07-02 16:10:15 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
#85,145,297
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x4d8dc985
#2
0x39435dac
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#6
0xed82b078
#7
0x6a468dde
#8
setData
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd31d7e43…0b56
0x34b655…2a6f
4 touches
1 conflict
0xac61c3cf…cf4f
0x34b655…2a6f
4 touches
1 conflict
0x2406ccf7…c1cb
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x009177df…4ecc
0x34b655…2a6f
2 touches
0 conflicts
0x0b2a838b…287c
0x34b655…2a6f
2 touches
0 conflicts
0x2c58327f…7726
0x34b655…2a6f
2 touches
0 conflicts
0x30153288…6d46
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
0xd31d7e43b9…6c0b56
Audit this contract →
← previous block
·
next block →
recent activity