pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,837,628
← previous block
next block →
recent activity
Analyzing
Block #89,837,628
9 transactions · 9 stateful · 2026-07-24 05:49:01 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,837,628
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6ad2e98b
#2
updatePrices
#3
executeBatch
#4
execFwdPositionOps
#5
0x1fe271b4
· blocks 2
#8
updateDataFeedsValuesPartial
#6
0x1fe271b4
· blocks 1
#7
0x1fe271b4
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7873c33c…28c1
0x0a2fbf…29b1
6 touches
3 conflicts
0xd0b4282c…f30c
0x0a2fbf…29b1
6 touches
3 conflicts
0xd0b4282c…f30d
0x0a2fbf…29b1
6 touches
3 conflicts
0xd0b4282c…f310
0x0a2fbf…29b1
6 touches
3 conflicts
0x00000000…0006
0x0a2fbf…29b1
6 touches
3 conflicts
0x00000000…0005
0x370e2e…63b4
6 touches
3 conflicts
0x86d8b042…8fb4
0x370e2e…63b4
6 touches
3 conflicts
0x1bff683e…7ecb
0x754704…b603
6 touches
3 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
3 conflicts on slot
0x7873c33c0f…b428c1
Audit this contract →
← previous block
·
next block →
recent activity