pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,438,559
← previous block
next block →
recent activity
Analyzing
Block #74,438,559
9 transactions · 7 stateful · 2026-05-14 01:35:21 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,438,559
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
redeemDelegations
#5
setData
#6
0x5339c59f
· blocks 1
#7
0xed82b078
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0c7142f7…ef91
0x065c9d…c394
2 touches
0 conflicts
0x0ff217ef…2e68
0x065c9d…c394
2 touches
0 conflicts
0x8ffcccd9…df64
0x065c9d…c394
2 touches
0 conflicts
0x935f1cbf…8881
0x065c9d…c394
2 touches
0 conflicts
0x2e2214a9…fe0d
0x5d823e…89c6
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity