pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,796,662
← previous block
next block →
recent activity
Analyzing
Block #75,796,662
11 transactions · 8 stateful · 2026-05-20 08:54:05 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,796,662
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
redeemDelegations
#3
0x0f6795d9
#4
forward
#5
0x0f6795d9
#6
0xe9316489
· blocks 1
#8
setData
#9
0x85be78…4de1
#10
0x46927d…1edc
#7
0xe9316489
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92a0110c…88c6
0x96b79e…d00a
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x0ff906…10e8
2 touches
0 conflicts
0x5583aed2…de2c
0x34b655…2a6f
2 touches
0 conflicts
0x586ab01d…fbc4
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
0x34b655…2a6f
2 touches
0 conflicts
0xa176d22f…9aa8
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:
0x96b79ef4…d2d00a
1 conflict on slot
0x92a0110cab…9188c6
Audit this contract →
← previous block
·
next block →
recent activity