pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,747,889
← previous block
next block →
recent activity
Analyzing
Block #89,747,889
9 transactions · 7 stateful · 2026-07-23 22:16:02 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,747,889
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 2
#5
0x0f6795d9
#6
transfer
#7
setData
#8
0x41eaca…e728
#3
0x0f6795d9
· blocks 1
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffb0af0f…eaa9
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0x1e10796e…6214
0x34b655…2a6f
2 touches
0 conflicts
0x2f81ca21…67d7
0x34b655…2a6f
2 touches
0 conflicts
0x48b13e5e…3c2a
0x34b655…2a6f
2 touches
0 conflicts
0x911c55e7…ded4
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
3 conflicts on slot
0xffb0af0fe0…caeaa9
Audit this contract →
← previous block
·
next block →
recent activity