pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,572,887
← previous block
next block →
recent activity
Analyzing
Block #89,572,887
10 transactions · 8 stateful · 2026-07-23 05:15:04 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,572,887
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
#7
0xe9316489
#8
0xe9316489
#9
setData
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a36cb2e…0929
0x34b655…2a6f
4 touches
1 conflict
0x5297aa98…7b76
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x79af9c18…da95
0x34b655…2a6f
4 touches
1 conflict
0x8fb14d9e…6ed3
0x34b655…2a6f
4 touches
1 conflict
0x5297aa98…7b75
0x34b655…2a6f
4 touches
1 conflict
0xee590bfa…11b5
0x34b655…2a6f
3 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:
Perpl
1 conflict on slot
0x9a36cb2e52…470929
Audit this contract →
← previous block
·
next block →
recent activity