pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,418,763
← previous block
next block →
recent activity
Analyzing
Block #74,418,763
11 transactions · 9 stateful · 2026-05-13 23:23:31 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,418,763
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x98717539
#4
collect
#5
setData
#6
delegate
#7
0xed82b078
#8
exactInputSingle
#9
0x6a05086b
· blocks 1
#10
0x6a05086b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xdbda45e3…d2e4
0x019883…2a9a
2 touches
0 conflicts
0xdbda45e3…d2e5
0x019883…2a9a
2 touches
0 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
2 touches
0 conflicts
0xe527656e…2164
0x139aab…382b
2 touches
0 conflicts
0xe527656e…2165
0x139aab…382b
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