pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,573,953
← previous block
next block →
recent activity
Analyzing
Block #84,573,953
11 transactions · 9 stateful · 2026-06-30 00:39:22 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
#84,573,953
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xb5ce855a
#2
0xab083028
· blocks 1
#4
updatePrices
#5
0x39435dac
#6
updateDataFeedsValuesPartial
#7
0x0f6795d9
#8
forward
#9
setData
#10
0x39435dac
#3
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53e50026…6d8c
0x69df8a…6292
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x46279ae7…20dd
0x69df8a…6292
4 touches
1 conflict
0xa9db7b4d…2957
0x40c49f…2af0
4 touches
1 conflict
0xdfc5f346…7b42
0x40c49f…2af0
4 touches
1 conflict
0x213ee207…a151
0x69df8a…6292
4 touches
1 conflict
0xae5e6f9a…2991
0xc8689a…ee79
4 touches
1 conflict
0x7f4a8466…f2cc
0x69df8a…6292
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:
0x69df8a43…506292
1 conflict on slot
0x53e5002666…916d8c
Audit this contract →
← previous block
·
next block →
recent activity