pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,513,366
← previous block
next block →
recent activity
Analyzing
Block #85,513,366
11 transactions · 9 stateful · 2026-07-04 09:01:21 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,513,366
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xc1d7f479
· blocks 1
#3
0xab083028
#4
updateDataFeedsValuesPartial
#5
updatePrices
#6
0x3f5c179b
#7
forward
#8
forward
#9
setData
#10
0xe5c5ca…cf92
#2
0xc1d7f479
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000b
0x90c374…be45
4 touches
1 conflict
0x00000000…000a
0x90c374…be45
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x8876d94c…8435
0x2a68ba…90c5
2 touches
0 conflicts
0xa15bc60c…054d
0x336ed4…c59c
2 touches
0 conflicts
0xcbc4e5fb…95b0
0x336ed4…c59c
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:
0x90c3747c…0ebe45
1 conflict on slot
0x0000000000…00000b
Audit this contract →
← previous block
·
next block →
recent activity