pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,954,719
← previous block
next block →
recent activity
Analyzing
Block #75,954,719
10 transactions · 9 stateful · 2026-05-21 02:28:15 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,954,719
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
0x98717539
· blocks 1
#4
exec
#5
0x0f6795d9
#6
0x0f6795d9
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x39435dac
#3
0x98717539
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
0x0711ec2d…d973
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x8d66a4…3095
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x9abd5cd0…9d1d
0x8d66a4…3095
3 touches
1 conflict
0x8a35acfb…d1a6
0x8d66a4…3095
3 touches
1 conflict
0x10f5f4d8…572e
0x34b655…2a6f
2 touches
0 conflicts
0x2b1efc13…7de3
0x34b655…2a6f
2 touches
0 conflicts
0x2eafd046…57f8
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:
Perpl
1 conflict on slot
0x0711ec2d85…d3d973
Audit this contract →
← previous block
·
next block →
recent activity