pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,750,850
← previous block
next block →
recent activity
Analyzing
Block #89,750,850
16 transactions · 15 stateful · 2026-07-23 22:31:01 UTC
Parallelism
88
/100
Blocked
7
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,750,850
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#4
CreateMemory
#5
CreateMemory
#6
CreateMemory
#7
CreateMemory
#8
CreateMemory
#9
CreateMemory
#10
CreateMemory
#11
CreateMemory
#12
CreateMemory
#13
CreateMemory
#15
setData
#14
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
14
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00f245ce…1e10
0x34b655…2a6f
2 touches
0 conflicts
0x2827cf71…013b
0x34b655…2a6f
2 touches
0 conflicts
0x2d76276f…7c66
0x34b655…2a6f
2 touches
0 conflicts
0x3270f906…a0e9
0x34b655…2a6f
2 touches
0 conflicts
0x3fb94afb…f955
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity