pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#89,864,680
← previous block
next block →
recent activity
Analyzing
Block #89,864,680
10 transactions · 10 stateful · 2026-07-24 08:05:12 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,864,680
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
0x5a5d9a99
#4
0x0f6795d9
· blocks 1
#5
0x3f5c179b
#6
0x3f5c179b
#8
0x6a631d30
#9
setData
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x438268c2…c849
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd9a2e985…9e28
0x34b655…2a6f
4 touches
1 conflict
0xeb0b1d43…9559
0x34b655…2a6f
4 touches
1 conflict
0x4ca2a6c3…ab80
0x34b655…2a6f
4 touches
1 conflict
0x02b3f3d1…4ece
0x34b655…2a6f
4 touches
1 conflict
0x438268c2…c848
0x34b655…2a6f
4 touches
1 conflict
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
0x438268c260…0ac849
Audit this contract →
← previous block
·
next block →
recent activity