pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,269,273
← previous block
next block →
recent activity
Analyzing
Block #75,269,273
8 transactions · 6 stateful · 2026-05-17 22:06:22 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,269,273
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
· blocks 1
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
redeemDelegations
#6
setData
#7
execOrders
#2
0x1ffa3c9b
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
0x50997ada…364d
0x5d823e…89c6
4 touches
1 conflict
0x2e2214a9…fe0d
0x5d823e…89c6
4 touches
1 conflict
0xc58b7e26…3c5a
0x065c9d…c394
4 touches
1 conflict
0x6b319071…a105
0xc8689a…ee79
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0xf0f673fd…37a7
0x5d823e…89c6
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
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:
0x5d823e99…9589c6
1 conflict on slot
0x50997ada44…ff364d
Audit this contract →
← previous block
·
next block →
recent activity