pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,752,015
← previous block
next block →
recent activity
Analyzing
Block #89,752,015
10 transactions · 7 stateful · 2026-07-23 22:36:53 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,752,015
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
#7
0x0f6795d9
#8
0x39435dac
#9
setData
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x48e3acd8…cf41
0x34b655…2a6f
4 touches
1 conflict
0xdec92f6c…f56d
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x067f4f24…bf80
0x34b655…2a6f
2 touches
0 conflicts
0x0852d43c…8c19
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94e9
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94ea
0x34b655…2a6f
2 touches
0 conflicts
0x374db62a…73d7
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
0x48e3acd863…7ecf41
Audit this contract →
← previous block
·
next block →
recent activity