pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,289,046
← previous block
next block →
recent activity
Analyzing
Block #90,289,046
9 transactions · 8 stateful · 2026-07-25 19:46:37 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,289,046
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
0x1fe271b4
· blocks 1
#6
execOrders
· blocks 1
#7
setData
#5
0x1fe271b4
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5775def6…60db
0x0a2fbf…29b1
4 touches
1 conflict
0x5775def6…60dc
0x0a2fbf…29b1
4 touches
1 conflict
0x00000000…0005
0x370e2e…63b4
4 touches
1 conflict
0xea5966cd…b51c
0x370e2e…63b4
4 touches
1 conflict
0x5775def6…60df
0x0a2fbf…29b1
4 touches
1 conflict
0x1bff683e…7ecb
0x754704…b603
4 touches
1 conflict
0x55b4e430…44cb
0x754704…b603
4 touches
1 conflict
0xbe047926…b03a
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
1 conflict on slot
0x5775def6e1…9360db
Audit this contract →
← previous block
·
next block →
recent activity