pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#89,573,463
← previous block
next block →
recent activity
Analyzing
Block #89,573,463
12 transactions · 11 stateful · 2026-07-23 05:18:55 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,573,463
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
#3
0x0f6795d9
· blocks 1
#4
0x0f6795d9
#5
updateDataFeedsValuesPartial
#7
0x57368ddf
#8
forward
#9
forward
#10
0x6a61a4b7
#11
setData
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x0bee8017…c90a
0x34b655…2a6f
2 touches
0 conflicts
0x0c9249f6…6bce
0x34b655…2a6f
2 touches
0 conflicts
0x0d07db71…c2e3
0x34b655…2a6f
2 touches
0 conflicts
0x1e10796e…6213
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
0xac2a02739b…81721b
Audit this contract →
← previous block
·
next block →
recent activity