pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,490,772
← previous block
next block →
recent activity
Analyzing
Block #76,490,772
12 transactions · 11 stateful · 2026-05-23 13:58:32 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,490,772
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
#2
0x6df9e92b
· blocks 1
#4
atInversebrah
#5
updateDataFeedsValuesPartial
#6
redeemDelegations
#7
0x0f6795d9
#8
0x0f6795d9
#9
setData
#10
updateTemporalNumericValuesV1
#11
transfer
#3
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0x2c492d…444e
4 touches
1 conflict
0x00000000…0000
0x2c492d…444e
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0xc740dd24…9801
0x3bd359…433a
4 touches
1 conflict
0x44ad89ba…cf83
0x5df178…7777
4 touches
1 conflict
0x73131ffc…b46c
0x5df178…7777
4 touches
1 conflict
0x41228885…9516
0x065c9d…c394
2 touches
0 conflicts
0xcc8faac2…c766
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:
0x2c492d8b…d3444e
1 conflict on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity