pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,182,638
← previous block
next block →
recent activity
Analyzing
Block #85,182,638
11 transactions · 11 stateful · 2026-07-02 20:18:53 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,182,638
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
0x5a5d9a99
· blocks 1
#5
execFwdPositionOps
#6
0x3f5c179b
#7
batchUpdate
#8
setData
#9
execOrders
· blocks 1
#4
execFwdPositionOps
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x9fc8b97d…96da
0x2a68ba…90c5
2 touches
0 conflicts
0x15cd6ce4…7154
0x34b655…2a6f
2 touches
0 conflicts
0x296e4bec…fa32
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity