pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,856,493
← previous block
next block →
recent activity
Analyzing
Block #89,856,493
10 transactions · 9 stateful · 2026-07-24 07:24:01 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,856,493
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
#3
0x0f6795d9
#4
0x1fe271b4
· blocks 2
#7
0xce1e7030
#8
0xed82b078
#9
setData
#5
0x1fe271b4
· blocks 1
#6
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9195a5d…140b
0x0a2fbf…29b1
6 touches
3 conflicts
0xe9195a5d…140a
0x0a2fbf…29b1
6 touches
3 conflicts
0x55b4e430…44cb
0x754704…b603
6 touches
3 conflicts
0xe9195a5d…140e
0x0a2fbf…29b1
6 touches
3 conflicts
0x00000000…0006
0x0a2fbf…29b1
6 touches
3 conflicts
0x1bff683e…7ecb
0x754704…b603
4 touches
1 conflict
0x00000000…0005
0x370e2e…63b4
4 touches
1 conflict
0xc15cbf16…348c
0x0a2fbf…29b1
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:
0x0a2fbf2d…f729b1
3 conflicts on slot
0xe9195a5d65…3f140b
Audit this contract →
← previous block
·
next block →
recent activity