pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#89,848,352
← previous block
next block →
recent activity
Analyzing
Block #89,848,352
9 transactions · 8 stateful · 2026-07-24 06:43:04 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,848,352
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x0f6795d9
#3
updateDataFeedsValuesPartial
#4
0x3b073534
· blocks 1
#6
0x6a6309f0
#7
setData
#8
0x39435dac
#5
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
4 touches
1 conflict
0xe41187bd…5f5c
0x0a2fbf…29b1
4 touches
1 conflict
0x55b4e430…44cb
0x754704…b603
4 touches
1 conflict
0xe41187bd…5f5d
0x0a2fbf…29b1
4 touches
1 conflict
0xe41187bd…5f60
0x0a2fbf…29b1
4 touches
1 conflict
0x2d071de0…c86e
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e66
0x34b655…2a6f
2 touches
0 conflicts
0x31d88d27…7617
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:
0x0a2fbf2d…f729b1
1 conflict on slot
0x0000000000…000006
Audit this contract →
← previous block
·
next block →
recent activity