pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,519,028
← previous block
next block →
recent activity
Analyzing
Block #74,519,028
13 transactions · 10 stateful · 2026-05-14 10:32:20 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,519,028
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
updatePrices
#4
0x98717539
#5
0x39abec6b
#6
updateDataFeedsValuesPartial
#7
commit
#8
0x0f7da9…3d88
#9
0x499ba9…c090
#10
setData
#11
redeemDelegations
#12
0x39435dac
#2
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x011bdd61…4318
0x2ab50b…5c41
2 touches
0 conflicts
0x09a8bb29…b290
0x2ab50b…5c41
2 touches
0 conflicts
0x1035ed1e…3885
0x2ab50b…5c41
2 touches
0 conflicts
0x132711dc…851a
0x2ab50b…5c41
2 touches
0 conflicts
0x13699c33…f787
0x2ab50b…5c41
2 touches
0 conflicts
0x15a8b5e6…0296
0x2ab50b…5c41
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:
0xab35264b…1cfa38
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity