pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,224,965
← previous block
next block →
recent activity
Analyzing
Block #74,224,965
12 transactions · 7 stateful · 2026-05-13 01:54:23 UTC
Parallelism
83
/100
Blocked
14
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,224,965
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0xbbb036a8
#3
exactInputSingle
#4
0x1094dc9f
#5
0x05ee6a22
#6
updateDataFeedsValuesPartial
#7
exactInputSingle
#8
setData
#9
0x34653439
#10
0x39435dac
#11
0xf2eaccd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d82c9b5…004c
0x3bd359…433a
4 touches
1 conflict
0x00000000…0003
0x5afd3e…7620
4 touches
1 conflict
0x4039b31f…0f4a
0x754704…b603
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x00000000…0005
0x5afd3e…7620
4 touches
1 conflict
0x47215b80…8f38
0x5afd3e…7620
4 touches
1 conflict
0xd59f6ed1…03eb
0x1b6862…e19c
2 touches
0 conflicts
0x30276c1c…47b4
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:
Wrapped MON (WMON)
1 conflict on slot
0x5d82c9b53a…be004c
Audit this contract →
← previous block
·
next block →
recent activity