pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,444,210
← previous block
next block →
recent activity
Analyzing
Block #76,444,210
9 transactions · 9 stateful · 2026-05-23 08:48:26 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,444,210
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
#2
0x98717539
#3
updateDataFeedsValuesPartial
#4
0x5339c59f
#5
0x5339c59f
· blocks 1
#7
redeemDelegations
#8
setData
#6
0x0c7abd22
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
0x8bc3e255…0a0b
0xa6afd3…d132
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x22863bf9…19df
0x34b655…2a6f
2 touches
0 conflicts
0x4d75d0b3…e59c
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x620b3893…9a32
0x34b655…2a6f
2 touches
0 conflicts
0x6dfb0062…8921
0x34b655…2a6f
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:
0xa6afd386…b0d132
1 conflict on slot
0x8bc3e2552c…6c0a0b
Audit this contract →
← previous block
·
next block →
recent activity