pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,103,646
← previous block
next block →
recent activity
Analyzing
Block #85,103,646
9 transactions · 9 stateful · 2026-07-02 11:31:41 UTC
Parallelism
44
/100
Blocked
44
%
Avg conflicts / tx
1.11
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,103,646
· 9 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0xab083028
#2
updatePrices
· blocks 4
#7
0x5a5d9a99
#8
0xc7e3ec2c
#3
updatePrices
· blocks 3
#4
updatePrices
· blocks 2
#5
updatePrices
· blocks 1
#6
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w3
6
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
10 touches
10 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x9fc8b97d…96da
0x2a68ba…90c5
2 touches
0 conflicts
0x58397d66…a6bc
0x34b655…2a6f
2 touches
0 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
2 touches
0 conflicts
0x997cacda…8b9a
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:
0x04fdeac2…f747d7
10 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity