pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,462,170
← previous block
next block →
recent activity
Analyzing
Block #74,462,170
9 transactions · 6 stateful · 2026-05-14 04:12:32 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,462,170
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
flash
· blocks 1
#2
0xed82b078
#3
updateDataFeedsValuesPartial
#5
0x6a054c28
#6
0xe4da58…498d
#7
setData
#8
0x631ff0…3100
#4
0xccf50a51
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaeb5864c…7679
0x2a68ba…90c5
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0xe8673279…b6cb
0x40c49f…2af0
4 touches
1 conflict
0x51ca3051…0972
0x3bd359…433a
2 touches
0 conflicts
0x76f2524a…306c
0x3bd359…433a
2 touches
0 conflicts
0x99f666e3…b2a2
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x614b85…a284
2 touches
0 conflicts
0x00000000…0002
0x614b85…a284
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:
0x2a68ba18…8e90c5
1 conflict on slot
0xaeb5864c20…607679
Audit this contract →
← previous block
·
next block →
recent activity