pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,684,779
← previous block
next block →
recent activity
Analyzing
Block #75,684,779
9 transactions · 7 stateful · 2026-05-19 20:29:47 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,684,779
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x98717539
· blocks 2
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#6
0x6a0cc8b3
#7
setData
#8
0xce2317…f3fa
#2
0x98717539
· blocks 1
#5
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x689cd5fd…5556
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x8d66a4…3095
4 touches
1 conflict
0x17cd1479…00bb
0x8d66a4…3095
3 touches
1 conflict
0x8a35acfb…d1a7
0x8d66a4…3095
3 touches
1 conflict
0x336241b2…c1db
0x34b655…2a6f
2 touches
0 conflicts
0x5728edaf…f1d4
0x34b655…2a6f
2 touches
0 conflicts
0x61f0d75b…4d77
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
3 conflicts on slot
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity