pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,503,402
← previous block
next block →
recent activity
Analyzing
Block #85,503,402
12 transactions · 11 stateful · 2026-07-04 07:55:08 UTC
Parallelism
75
/100
Blocked
27
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,503,402
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
setData
#6
updatePriceFeedsIfNecessary
#7
forward
#8
0x204ce421
· blocks 2
#11
0x6a48bcd3
#2
0x0c7abd22
#9
0xd65e8ff4
· blocks 1
#10
0x204ce421
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
8
w0
9
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0014
0x2f55a2…8375
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x44d7acbf…e67a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
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:
0x2f55a2e1…f48375
3 conflicts on slot
0x0000000000…000014
Audit this contract →
← previous block
·
next block →
recent activity