pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,774,081
← previous block
next block →
recent activity
Analyzing
Block #89,774,081
8 transactions · 8 stateful · 2026-07-24 00:28:19 UTC
Parallelism
63
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,774,081
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x6a62b21a
#7
setData
#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
0xb25cc7d3…a4ac
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x0b6605df…08f8
0x34b655…2a6f
2 touches
0 conflicts
0x2f8c826e…c115
0x34b655…2a6f
2 touches
0 conflicts
0x43cdca8f…780d
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
0xb25cc7d3f8…11a4ac
Audit this contract →
← previous block
·
next block →
recent activity