pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,951,568
← previous block
next block →
recent activity
Analyzing
Block #74,951,568
8 transactions · 5 stateful · 2026-05-16 10:43:57 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,951,568
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
· blocks 1
#3
redeemDelegations
#4
0x282fe4…0e02
#5
0xec91ad…d504
#6
setData
#7
execute
#2
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x10814d14…cdda
0x34b655…2a6f
2 touches
0 conflicts
0x1674d3d4…275f
0x34b655…2a6f
2 touches
0 conflicts
0x21b468a8…f015
0x34b655…2a6f
2 touches
0 conflicts
0x2c52beae…6a2c
0x34b655…2a6f
2 touches
0 conflicts
0x2fad73a1…ae09
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:
Perpl
1 conflict on slot
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity