pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,843,790
← previous block
next block →
recent activity
Analyzing
Block #85,843,790
13 transactions · 13 stateful · 2026-07-05 21:42:55 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,843,790
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x719d975a
· blocks 1
#3
0xab083028
#4
updatePrices
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x3f5c179b
#9
0x0f6795d9
#10
forward
#11
setData
#12
0x39435dac
#5
0x6c05cd2b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96a76165…f807
0x21e325…7777
4 touches
1 conflict
0xae3fbd28…a18c
0x3bd359…433a
4 touches
1 conflict
0xbc467e7a…af36
0x21e325…7777
4 touches
1 conflict
0x00000000…0000
0xe5a8f8…d7a8
4 touches
1 conflict
0x00000000…0002
0xe5a8f8…d7a8
4 touches
1 conflict
0x00000000…0003
0xe5a8f8…d7a8
4 touches
1 conflict
0x79e5e792…dfe6
0x11ed3b…2c96
4 touches
1 conflict
0x00000000…0000
0xef3a62…dd66
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:
0x21e325b0…3d7777
1 conflict on slot
0x96a7616557…64f807
Audit this contract →
← previous block
·
next block →
recent activity