pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,667,425
← previous block
next block →
recent activity
Analyzing
Block #89,667,425
8 transactions · 7 stateful · 2026-07-23 15:29:17 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,667,425
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
0x39435dac
#4
0x0f6795d9
#5
0x0f6795d9
#6
updateDataFeedsValuesPartial
#7
setData
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85d21fba…c8b2
0x34b655…2a6f
4 touches
1 conflict
0x5ea9eca9…22a7
0x34b655…2a6f
4 touches
1 conflict
0x43fd3667…094b
0x34b655…2a6f
4 touches
1 conflict
0x5ea9eca9…22a6
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x757b0543…e087
0x34b655…2a6f
4 touches
1 conflict
0x5e6e1eb6…ae55
0x34b655…2a6f
2 touches
0 conflicts
0x630f113e…c9c6
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
0x85d21fba47…9fc8b2
Audit this contract →
← previous block
·
next block →
recent activity