pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#77,349,240
← previous block
next block →
recent activity
Analyzing
Block #77,349,240
16 transactions · 11 stateful · 2026-05-27 13:17:59 UTC
Parallelism
88
/100
Blocked
9
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,349,240
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f052239
#2
updatePrices
#3
0x0487cb50
#4
0xed82b078
#5
redeemDelegations
· blocks 1
#7
0x62be7533
#8
0x0f6795d9
#9
0x0f6795d9
#10
updateDataFeedsValuesPartial
#11
updateDataFeedsValuesPartial
#12
0x3f5c179b
#13
forward
#14
0x6a16ef7f
#15
setData
#6
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x8c9f7a…17aa
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
0x18cf3003…51d1
0x065c9d…c394
2 touches
0 conflicts
0x3833c9c9…14dd
0x1111b3…4111
2 touches
0 conflicts
0x3eac71be…e886
0x1111b3…4111
2 touches
0 conflicts
0xad436b12…f632
0x1111b3…4111
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:
0x8c9f7a69…5317aa
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity