pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,700,924
← previous block
next block →
recent activity
Analyzing
Block #75,700,924
10 transactions · 10 stateful · 2026-05-19 22:16:54 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,700,924
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x98717539
#5
0x0c7abd22
#6
0x6a0ce1cd
· blocks 1
#7
setData
#9
0x39435dac
#2
0xab083028
#8
0x6a0ce1cd
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3ed11a18…1da9
0x065c9d…c394
4 touches
1 conflict
0x602a8267…cd30
0x065c9d…c394
4 touches
1 conflict
0x8944f217…7043
0x065c9d…c394
4 touches
1 conflict
0x41c1b066…4650
0x065c9d…c394
3 touches
1 conflict
0x65cc628c…56ce
0x065c9d…c394
3 touches
1 conflict
0x2f88a23f…9dc5
0x2a68ba…90c5
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity