pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,168,189
← previous block
next block →
recent activity
Analyzing
Block #85,168,189
11 transactions · 11 stateful · 2026-07-02 18:42:37 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,168,189
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x5bf9264c
· blocks 1
#5
0x5a5d9a99
#6
0x0f6795d9
#7
0x0f6795d9
#8
transfer
#9
setData
#10
0x39435dac
#4
0x5bf9264c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641c
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x16b3a441…13db
0x34b655…2a6f
2 touches
0 conflicts
0x260889f6…d2f6
0x34b655…2a6f
2 touches
0 conflicts
0x26918bca…6c75
0x34b655…2a6f
2 touches
0 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
2 touches
0 conflicts
0xa1144aa9…7f67
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
0xc824469a90…af641c
Audit this contract →
← previous block
·
next block →
recent activity