pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,901,718
← previous block
next block →
recent activity
Analyzing
Block #75,901,718
9 transactions · 4 stateful · 2026-05-20 20:35:32 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,901,718
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
redeemDelegations
· blocks 1
#4
0x0f6795d9
#5
0x0f6795d9
#6
setData
#7
0x67398c…dfe2
#8
0x7ffbb4…38b0
#3
redeemDelegations
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…0000
0x493596…2e64
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1684f8b4…ee31
0x34b655…2a6f
2 touches
0 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
2 touches
0 conflicts
0x3170a930…2681
0x34b655…2a6f
2 touches
0 conflicts
0x441ebe8e…c411
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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:
0x49359615…8b2e64
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity