pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,540,302
← previous block
next block →
recent activity
Analyzing
Block #89,540,302
9 transactions · 8 stateful · 2026-07-23 01:37:20 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,540,302
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#5
0x6a6170c8
#6
setData
#7
0x39435dac
#8
0xc7e3ec2c
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea6c2d78…6ac9
0x34b655…2a6f
4 touches
1 conflict
0xea91c4fe…1381
0x34b655…2a6f
4 touches
1 conflict
0xfcfb570f…cf1c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x23e706b3…0e16
0x34b655…2a6f
4 touches
1 conflict
0x25810cd9…9b59
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x79e8f935…c3b6
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0xea6c2d78b3…cb6ac9
Audit this contract →
← previous block
·
next block →
recent activity