pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#89,750,438
← previous block
next block →
recent activity
Analyzing
Block #89,750,438
10 transactions · 8 stateful · 2026-07-23 22:28:55 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,750,438
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
· blocks 2
#4
updateDataFeedsValuesPartial
#5
0x57368ddf
#6
0x0f6795d9
· blocks 1
#7
0x0f6795d9
#9
setData
#3
0x5a5d9a99
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xbb322930…ace5
0x34b655…2a6f
4 touches
1 conflict
0x110bfb60…31db
0x34b655…2a6f
2 touches
0 conflicts
0x48e3acd8…cf41
0x34b655…2a6f
2 touches
0 conflicts
0x4ee01e5b…3ace
0x34b655…2a6f
2 touches
0 conflicts
0x6e110cdf…7653
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity