pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,989,438
← previous block
next block →
recent activity
Analyzing
Block #75,989,438
10 transactions · 8 stateful · 2026-05-21 06:19:34 UTC
Parallelism
80
/100
Blocked
38
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,989,438
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
0x98717539
· blocks 1
#4
updateDataFeedsValuesPartial
#5
redeemDelegations
· blocks 1
#8
execFwdPositionOps
#9
setData
#2
updatePrices
#6
redeemDelegations
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
5
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x7b8d2a…7e83
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x61571888…b392
0x34b655…2a6f
4 touches
1 conflict
0x0a809ce1…7894
0x34b655…2a6f
2 touches
0 conflicts
0x0b21ddd5…a306
0x34b655…2a6f
2 touches
0 conflicts
0x1a44398b…cf39
0x34b655…2a6f
2 touches
0 conflicts
0x33450100…bcf0
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:
0x7b8d2a95…7f7e83
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity