pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,483,167
← previous block
next block →
recent activity
Analyzing
Block #74,483,167
9 transactions · 8 stateful · 2026-05-14 06:32:10 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,483,167
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x9e76c652
#2
0x39435dac
· blocks 2
#3
updateDataFeedsValuesPartial
#4
fulfillOutcomes
#5
0x6a056ce1
#6
setData
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x309ef367…e8a1
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0006
0x2ab50b…5c41
2 touches
0 conflicts
0x0dbc153f…25c5
0x2ab50b…5c41
2 touches
0 conflicts
0x23026701…a705
0x2ab50b…5c41
2 touches
0 conflicts
0x288844c6…2590
0x2ab50b…5c41
2 touches
0 conflicts
0x292270fc…35dd
0x2ab50b…5c41
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity