pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,440,083
← previous block
next block →
recent activity
Analyzing
Block #74,440,083
13 transactions · 10 stateful · 2026-05-14 01:45:29 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,440,083
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x67098489
· blocks 1
#4
approve
#5
0x1094dc9f
#6
0x05ee6a22
#7
updateDataFeedsValuesPartial
#8
forward
#9
0xed82b078
#10
0x6a0529b1
#11
setData
#12
0x39435dac
#3
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x641245e3…6323
0xc8689a…ee79
4 touches
1 conflict
0xba5743c7…21c2
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xc65cd8f1…8f81
0xd32edf…ff58
3 touches
1 conflict
0x01e7b865…6e70
0x188d58…ea8e
2 touches
0 conflicts
0x05b0e27c…001d
0x188d58…ea8e
2 touches
0 conflicts
0x05b0e27c…001e
0x188d58…ea8e
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:
0x1b68626d…2de19c
1 conflict on slot
0x0000000000…000013
Audit this contract →
← previous block
·
next block →
recent activity