pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,838,535
← previous block
next block →
recent activity
Analyzing
Block #89,838,535
10 transactions · 9 stateful · 2026-07-24 05:53:35 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,838,535
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x5a5d9a99
#4
0x0f6795d9
#5
0x1fe271b4
· blocks 1
#7
0x57368ddf
#8
setData
#9
0x39435dac
#6
0x1fe271b4
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec18370e…d64b
0x370e2e…63b4
4 touches
1 conflict
0x1bff683e…7ecb
0x754704…b603
4 touches
1 conflict
0x55b4e430…44cb
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x0a2fbf…29b1
4 touches
1 conflict
0x12a18c49…8b68
0x0a2fbf…29b1
4 touches
1 conflict
0x12a18c49…8b69
0x0a2fbf…29b1
4 touches
1 conflict
0xf77c1719…03e0
0x0a2fbf…29b1
4 touches
1 conflict
0xf77c1719…03e1
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:
0x370e2ee6…bd63b4
1 conflict on slot
0xec18370e3e…eed64b
Audit this contract →
← previous block
·
next block →
recent activity