pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,789,351
← previous block
next block →
recent activity
Analyzing
Block #74,789,351
11 transactions · 11 stateful · 2026-05-15 16:41:24 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,789,351
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x1a945f9c
· blocks 1
#5
0x98717539
#7
0x6a074d2b
#8
setData
#9
redeemDelegations
#10
execOrders
#6
0xd10227eb
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8abcc19…3d83
0xea1b8e…c5ec
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0272738f…1da6
0x065c9d…c394
2 touches
0 conflicts
0x24ff2609…4684
0x065c9d…c394
2 touches
0 conflicts
0x60cfe676…8c43
0x065c9d…c394
2 touches
0 conflicts
0x9e8f801d…a1dc
0x065c9d…c394
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:
LeverUp: LeverUp
1 conflict on slot
0xa8abcc1955…203d83
Audit this contract →
← previous block
·
next block →
recent activity