pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,864,181
← previous block
next block →
recent activity
Analyzing
Block #75,864,181
11 transactions · 6 stateful · 2026-05-20 16:25:42 UTC
Parallelism
82
/100
Blocked
17
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,864,181
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
0x98717539
#4
redeemDelegations
· blocks 1
#6
updateDataFeedsValuesPartial
#7
setData
#8
0xcd1701…3aba
#9
0x5451c9…beb2
#10
0x39435dac
#5
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x5749b3…10b4
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0711ec2d…d973
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x5728edaf…f1d4
0x34b655…2a6f
2 touches
0 conflicts
0x578e7f66…1b56
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
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:
0x5749b3be…3810b4
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity