pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,946,926
← previous block
next block →
recent activity
Analyzing
Block #75,946,926
9 transactions · 8 stateful · 2026-05-21 01:36:27 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,946,926
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
0xbb5d006a
· blocks 1
#4
0xed82b078
#5
redeemDelegations
#6
setData
#7
updatePosition
#8
0xed82b078
#3
0xbb5d006a
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
0x3f56e962…eadb
0x541997…f5a0
4 touches
1 conflict
0x3f56e962…eadc
0x541997…f5a0
4 touches
1 conflict
0x5b87c6f2…9d52
0x541997…f5a0
3 touches
1 conflict
0x24781048…4772
0x2a68ba…90c5
2 touches
0 conflicts
0x76e96198…eec4
0x2a68ba…90c5
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0xa27fa22d…7dca
0x54cd53…9e7d
2 touches
0 conflicts
0x37809ed6…0d6d
0x6657d1…8ccc
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:
0x541997e9…30f5a0
1 conflict on slot
0x3f56e962a9…78eadb
Audit this contract →
← previous block
·
next block →
recent activity