pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#89,689,752
← previous block
next block →
recent activity
Analyzing
Block #89,689,752
10 transactions · 8 stateful · 2026-07-23 17:22:36 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,689,752
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
0x0f6795d9
#3
updateDataFeedsValuesPartial
#5
0xce1e7030
#6
0x57368ddf
#7
0x0f6795d9
#8
0xf5d05576
#9
setData
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc73549e8…2001
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x021afc04…da69
0x34b655…2a6f
2 touches
0 conflicts
0x2a6ce996…6902
0x34b655…2a6f
2 touches
0 conflicts
0x2b173c46…08b1
0x34b655…2a6f
2 touches
0 conflicts
0x623fd48c…9d77
0x34b655…2a6f
2 touches
0 conflicts
0x734ee320…caae
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0xc73549e8bd…582001
Audit this contract →
← previous block
·
next block →
recent activity