pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,978,805
← previous block
next block →
recent activity
Analyzing
Block #74,978,805
11 transactions · 11 stateful · 2026-05-16 13:46:43 UTC
Parallelism
73
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,978,805
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x98717539
#4
0x98717539
#5
redeemDelegations
#6
updateDataFeedsValuesPartial
#8
0x5339c59f
#9
0x6a0875ba
#10
setData
#2
0xed82b078
· blocks 1
#7
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99674e31…430a
0x065c9d…c394
4 touches
1 conflict
0xd942c9e1…b2ae
0x065c9d…c394
3 touches
1 conflict
0x1104a110…a650
0x065c9d…c394
3 touches
1 conflict
0x09f8192f…948f
0x065c9d…c394
3 touches
1 conflict
0xc6c107a7…4033
0x065c9d…c394
3 touches
1 conflict
0x6c0dd2c6…4813
0x065c9d…c394
2 touches
0 conflicts
0xeea81611…4df6
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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: Market-MON/USDC
1 conflict on slot
0x99674e3184…a2430a
Audit this contract →
← previous block
·
next block →
recent activity